Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 940faf80f53e14b88896ffd81f5d7e291ee107fe11e3b35de71df559fa574928

Tx prefix hash: 83ad8f407dfef39d72ad2da0ef48427fba3d73d120e368c050af32b108ac3b3e
Tx public key: ad602ccf1e261c0670056f11f0b2e6f5f69eb94c3b0f1061ff20082db85d91a3
Timestamp: 1703125272 Timestamp [UCT]: 2023-12-21 02:21:12 Age [y:d:h:m:s]: 01:108:16:41:16
Block: 917670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338785 RingCT/type: yes/0
Extra: 01ad602ccf1e261c0670056f11f0b2e6f5f69eb94c3b0f1061ff20082db85d91a3021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0c5e7081104ab053eedc8d32aa4160f33f547a63eddf25d76454a6d5e96085a 0.600000000000 1375252 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": 917680, "vin": [ { "gen": { "height": 917670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0c5e7081104ab053eedc8d32aa4160f33f547a63eddf25d76454a6d5e96085a" } } ], "extra": [ 1, 173, 96, 44, 207, 30, 38, 28, 6, 112, 5, 111, 17, 240, 178, 230, 245, 246, 158, 185, 76, 59, 15, 16, 97, 255, 32, 8, 45, 184, 93, 145, 163, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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