Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af59bd774aad9ed5393be6a4585b06e5d2c90a7fa8e0398b9dbf6bbf7363e4bb

Tx prefix hash: 65f75d0329f6b7fb998090ab2407e83436e0d930070384889f25c324ba8a63a9
Tx public key: c642e57c098427d41b8d23b74c57eabe9518604f5f8e5dee274fa762a7aee613
Timestamp: 1726772508 Timestamp [UCT]: 2024-09-19 19:01:48 Age [y:d:h:m:s]: 00:199:04:30:21
Block: 1113697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142171 RingCT/type: yes/0
Extra: 01c642e57c098427d41b8d23b74c57eabe9518604f5f8e5dee274fa762a7aee61302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7fff810196a3e4c1e8444513e53db3bfc6d22ab33f1d278921264da0ff917c9 0.600000000000 1593466 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": 1113707, "vin": [ { "gen": { "height": 1113697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7fff810196a3e4c1e8444513e53db3bfc6d22ab33f1d278921264da0ff917c9" } } ], "extra": [ 1, 198, 66, 229, 124, 9, 132, 39, 212, 27, 141, 35, 183, 76, 87, 234, 190, 149, 24, 96, 79, 95, 142, 93, 238, 39, 79, 167, 98, 167, 174, 230, 19, 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