Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b6cb3aec040ba1a4653667d91ce850ae0f41a404c36b795a4554bd681715134

Tx prefix hash: 3afd1d31d2d114a28da7ace4be1c9c52dad9946026b830b27d866f777d3d71b1
Tx public key: a613f4021d0645e13c7f7f621138b4eca23fa3334b628eca65873184d82bce01
Timestamp: 1714953770 Timestamp [UCT]: 2024-05-06 00:02:50 Age [y:d:h:m:s]: 00:138:12:49:34
Block: 1015717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99243 RingCT/type: yes/0
Extra: 01a613f4021d0645e13c7f7f621138b4eca23fa3334b628eca65873184d82bce010211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2de62792cf517eaa1b334e405da2d8c797e6fd024a44438ef339f1d5c31287 0.600000000000 1479156 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": 1015727, "vin": [ { "gen": { "height": 1015717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2de62792cf517eaa1b334e405da2d8c797e6fd024a44438ef339f1d5c31287" } } ], "extra": [ 1, 166, 19, 244, 2, 29, 6, 69, 225, 60, 127, 127, 98, 17, 56, 180, 236, 162, 63, 163, 51, 75, 98, 142, 202, 101, 135, 49, 132, 216, 43, 206, 1, 2, 17, 0, 0, 0, 4, 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