Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6226cc4575183c5ebfe06cb3682e7b311a7e3a5915aa42eccd84c19fc511d7d

Tx prefix hash: ff41e3bea05a5cdf6bf21bf96edbb4402ab45e38a3de22aa8648f71a9c7e366b
Tx public key: beb17c8cbcb3f98ad27f357cc46c2d694f235d0bd573f589eff3edfeab373bae
Timestamp: 1736516168 Timestamp [UCT]: 2025-01-10 13:36:08 Age [y:d:h:m:s]: 00:126:03:36:15
Block: 1194343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89959 RingCT/type: yes/0
Extra: 01beb17c8cbcb3f98ad27f357cc46c2d694f235d0bd573f589eff3edfeab373bae0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 720deb057c81d5c6eb86d29b3c5430511abc04aa7e3471de9d3591f32f2253ce 0.600000000000 1680912 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": 1194353, "vin": [ { "gen": { "height": 1194343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "720deb057c81d5c6eb86d29b3c5430511abc04aa7e3471de9d3591f32f2253ce" } } ], "extra": [ 1, 190, 177, 124, 140, 188, 179, 249, 138, 210, 127, 53, 124, 196, 108, 45, 105, 79, 35, 93, 11, 213, 115, 245, 137, 239, 243, 237, 254, 171, 55, 59, 174, 2, 17, 0, 0, 0, 7, 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