Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef6c80422939bb4f25b7b69eac4c5ddded22e81d877873ca09843f08f305c773

Tx prefix hash: 279b1cd7d1c6b2a2473943833f5bbbf673b9f2f73a6cac18df9f53569dec5995
Tx public key: 9369fb50b47ac4a70cb31f13886315ac268059077cbb5de1c55a50d2531e6768
Timestamp: 1710517587 Timestamp [UCT]: 2024-03-15 15:46:27 Age [y:d:h:m:s]: 01:018:09:52:48
Block: 978964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274112 RingCT/type: yes/0
Extra: 019369fb50b47ac4a70cb31f13886315ac268059077cbb5de1c55a50d2531e67680211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5fd2d13fdb0e95488be2dac15d87576e525ba90d8e573231dcd631b3280d31e 0.600000000000 1438993 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": 978974, "vin": [ { "gen": { "height": 978964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5fd2d13fdb0e95488be2dac15d87576e525ba90d8e573231dcd631b3280d31e" } } ], "extra": [ 1, 147, 105, 251, 80, 180, 122, 196, 167, 12, 179, 31, 19, 136, 99, 21, 172, 38, 128, 89, 7, 124, 187, 93, 225, 197, 90, 80, 210, 83, 30, 103, 104, 2, 17, 0, 0, 0, 6, 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