Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6e752330e83839a4e685da7a554c0e40f8c3c2a953c1216c1cc8276950eadde

Tx prefix hash: 60d2d69924616c5935946965962b070d37f8b2f10df4f549a1d79957c98b376a
Tx public key: 0dc2184b0a6bfb166c61efee860447ce9489706b37469ea8390f1c8fe9d4df4a
Timestamp: 1711397570 Timestamp [UCT]: 2024-03-25 20:12:50 Age [y:d:h:m:s]: 01:050:10:17:37
Block: 986254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297030 RingCT/type: yes/0
Extra: 010dc2184b0a6bfb166c61efee860447ce9489706b37469ea8390f1c8fe9d4df4a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b662f2a3fe751259a744f772bb1596501e8eda6fc74f34a806bfa59138ceae86 0.600000000000 1446483 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": 986264, "vin": [ { "gen": { "height": 986254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b662f2a3fe751259a744f772bb1596501e8eda6fc74f34a806bfa59138ceae86" } } ], "extra": [ 1, 13, 194, 24, 75, 10, 107, 251, 22, 108, 97, 239, 238, 134, 4, 71, 206, 148, 137, 112, 107, 55, 70, 158, 168, 57, 15, 28, 143, 233, 212, 223, 74, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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