Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b1fa8c74f632d1a40469364fe0380fa3c3a137251dfb4423e2108c93a7ea232

Tx prefix hash: 4967e9ee3d560858b9b1674f283be464030dafb1ef09a3754645eec025056e69
Tx public key: ed748113feb1e9b2c73ed24414f1741e62d0a80fb12163247a553cb3d45274f5
Timestamp: 1729959920 Timestamp [UCT]: 2024-10-26 16:25:20 Age [y:d:h:m:s]: 00:150:13:51:53
Block: 1140096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107391 RingCT/type: yes/0
Extra: 01ed748113feb1e9b2c73ed24414f1741e62d0a80fb12163247a553cb3d45274f502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb54d28212c65214833a8cac6b22cfaeebe3e09a455d0ce1e0c66e7dc04a3e58 0.600000000000 1623887 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": 1140106, "vin": [ { "gen": { "height": 1140096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb54d28212c65214833a8cac6b22cfaeebe3e09a455d0ce1e0c66e7dc04a3e58" } } ], "extra": [ 1, 237, 116, 129, 19, 254, 177, 233, 178, 199, 62, 210, 68, 20, 241, 116, 30, 98, 208, 168, 15, 177, 33, 99, 36, 122, 85, 60, 179, 212, 82, 116, 245, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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