Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596e3fb56187246dcee107996ebfc56f00de490f7207a55932ce3be1e90215c8

Tx prefix hash: bf0a7e93c0a15ce478df312534c765c360b59b9b4bf41738b7236c838dd37c71
Tx public key: cb3e56376220760b4d449cfda8bc8262b34ee825d2cbc5aa5abe53bb7d7946c4
Timestamp: 1726682584 Timestamp [UCT]: 2024-09-18 18:03:04 Age [y:d:h:m:s]: 00:195:03:32:20
Block: 1112954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139282 RingCT/type: yes/0
Extra: 01cb3e56376220760b4d449cfda8bc8262b34ee825d2cbc5aa5abe53bb7d7946c402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87a54fd61e3350f021934e9224d7fc518e6b728a915fb992a91e62c1fdc31ada 0.600000000000 1592457 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": 1112964, "vin": [ { "gen": { "height": 1112954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87a54fd61e3350f021934e9224d7fc518e6b728a915fb992a91e62c1fdc31ada" } } ], "extra": [ 1, 203, 62, 86, 55, 98, 32, 118, 11, 77, 68, 156, 253, 168, 188, 130, 98, 179, 78, 232, 37, 210, 203, 197, 170, 90, 190, 83, 187, 125, 121, 70, 196, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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