Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd31408882f83c61222adeba9bf8558b4fffd0ec5737b041eb896d06906175a

Tx prefix hash: 6ab1addeb6e10a1b58aa7060dd4c902352f4455c5f88113260c4c1f0369cbb3b
Tx public key: 64fa907c374e2dd4b8fdfa12db1ce10e591f4dae410b4651a3e146dda1ab3bd1
Timestamp: 1726999123 Timestamp [UCT]: 2024-09-22 09:58:43 Age [y:d:h:m:s]: 00:110:10:12:34
Block: 1115584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78959 RingCT/type: yes/0
Extra: 0164fa907c374e2dd4b8fdfa12db1ce10e591f4dae410b4651a3e146dda1ab3bd1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 683e590a75987055844106f6a8bc03c0b1fdc70c0d15ff13d455a7abc9578091 0.600000000000 1595769 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": 1115594, "vin": [ { "gen": { "height": 1115584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "683e590a75987055844106f6a8bc03c0b1fdc70c0d15ff13d455a7abc9578091" } } ], "extra": [ 1, 100, 250, 144, 124, 55, 78, 45, 212, 184, 253, 250, 18, 219, 28, 225, 14, 89, 31, 77, 174, 65, 11, 70, 81, 163, 225, 70, 221, 161, 171, 59, 209, 2, 17, 0, 0, 0, 3, 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