Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17431a9df3d6709812af8799aeb1b85830d85903142d8ebd5a4bb7f0bb1b0fe

Tx prefix hash: e651cd8bea35baefc609da74af5ff7f76ecd146c12e862a263fbc80c95de4b41
Tx public key: b4fa0938b100704c687e13f6e93e0fca533eed4d5a8518b295602b587374b2fe
Timestamp: 1720464987 Timestamp [UCT]: 2024-07-08 18:56:27 Age [y:d:h:m:s]: 00:311:02:51:08
Block: 1061415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222315 RingCT/type: yes/0
Extra: 01b4fa0938b100704c687e13f6e93e0fca533eed4d5a8518b295602b587374b2fe021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38428c0d0a514547fe985155b094ed8c91a732ef14e4dbe5acbd2c873f1f8c3a 0.600000000000 1531906 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": 1061425, "vin": [ { "gen": { "height": 1061415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38428c0d0a514547fe985155b094ed8c91a732ef14e4dbe5acbd2c873f1f8c3a" } } ], "extra": [ 1, 180, 250, 9, 56, 177, 0, 112, 76, 104, 126, 19, 246, 233, 62, 15, 202, 83, 62, 237, 77, 90, 133, 24, 178, 149, 96, 43, 88, 115, 116, 178, 254, 2, 17, 0, 0, 0, 7, 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