Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac47e4fc9d07d129073c61d175cd870949b58698fc16e7d18dc4d841d00dcb71

Tx prefix hash: b547c342a93340e1365ecce9138f64d40b451355b51df6c89034d2d1f4daccd3
Tx public key: 636a9efce9b737ca20272f5d07352b4afd5a89142d8f54e10ab99c3d64929f0d
Timestamp: 1708217293 Timestamp [UCT]: 2024-02-18 00:48:13 Age [y:d:h:m:s]: 01:040:06:03:18
Block: 959861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289802 RingCT/type: yes/0
Extra: 01636a9efce9b737ca20272f5d07352b4afd5a89142d8f54e10ab99c3d64929f0d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3576ac72a80d0264359eaa3b612a9c4bcdfcbc049f0bdbe71c8bc55869073e04 0.600000000000 1419420 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": 959871, "vin": [ { "gen": { "height": 959861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3576ac72a80d0264359eaa3b612a9c4bcdfcbc049f0bdbe71c8bc55869073e04" } } ], "extra": [ 1, 99, 106, 158, 252, 233, 183, 55, 202, 32, 39, 47, 93, 7, 53, 43, 74, 253, 90, 137, 20, 45, 143, 84, 225, 10, 185, 156, 61, 100, 146, 159, 13, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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