Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 91c12b4e9ae0924175ca2b02095cff9e3d1a19d5d72998534f79f14f950c92a2

Tx prefix hash: ba94f103a2e6c120ee5738f0fba5e7841a61ff2ac16cb26340c2c5c3ee9c9ec7
Tx public key: a77e6185ba326d8fe6b07a3875e83dded855ee9d79503a936beefbc25d1530bf
Timestamp: 1723385718 Timestamp [UCT]: 2024-08-11 14:15:18 Age [y:d:h:m:s]: 00:222:13:42:48
Block: 1085627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158948 RingCT/type: yes/0
Extra: 01a77e6185ba326d8fe6b07a3875e83dded855ee9d79503a936beefbc25d1530bf02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f482fa7315e522e7851c182308b9097f47478adc956b62231fdf8b4c739fd1 0.600000000000 1560214 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1085637, "vin": [ { "gen": { "height": 1085627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f482fa7315e522e7851c182308b9097f47478adc956b62231fdf8b4c739fd1" } } ], "extra": [ 1, 167, 126, 97, 133, 186, 50, 109, 143, 230, 176, 122, 56, 117, 232, 61, 222, 216, 85, 238, 157, 121, 80, 58, 147, 107, 238, 251, 194, 93, 21, 48, 191, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8