Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01fe1d41f55df87d3e66122d52b4f359045784148e4356c42db4c1c34bfbe037

Tx prefix hash: ca7ec2f77d24ad2be4d7c1a96feb22d096d8ba815eec56500fed66cb477400b9
Tx public key: b437c6c5d2ce328ae64859545d5007ba78dcb80d72032be2d70ab5aa75e4bd4e
Timestamp: 1713014518 Timestamp [UCT]: 2024-04-13 13:21:58 Age [y:d:h:m:s]: 00:318:16:44:34
Block: 999626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227831 RingCT/type: yes/0
Extra: 01b437c6c5d2ce328ae64859545d5007ba78dcb80d72032be2d70ab5aa75e4bd4e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3c4428e51429044b841d808502212e866a4d1e460614d2941145ff0234ee851 0.600000000000 1460108 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": 999636, "vin": [ { "gen": { "height": 999626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3c4428e51429044b841d808502212e866a4d1e460614d2941145ff0234ee851" } } ], "extra": [ 1, 180, 55, 198, 197, 210, 206, 50, 138, 230, 72, 89, 84, 93, 80, 7, 186, 120, 220, 184, 13, 114, 3, 43, 226, 215, 10, 181, 170, 117, 228, 189, 78, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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