Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 546c0de737e773ecef0bd7b6fd1eb085a8c2967ae6fc04c81b954d4b82fb9acf

Tx prefix hash: 72b9f238182c936a6e0b25be0b2f4f09a9e6b37f3c67bf02d6762bc99108100f
Tx public key: cddd3297cb85f43e909ca63bf910fede8cca4efb4e0325da2e805564296333c3
Timestamp: 1710445921 Timestamp [UCT]: 2024-03-14 19:52:01 Age [y:d:h:m:s]: 01:037:16:09:17
Block: 978364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287897 RingCT/type: yes/0
Extra: 01cddd3297cb85f43e909ca63bf910fede8cca4efb4e0325da2e805564296333c302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63128ed99997aeefbed31a0d73d04fe9b61d61668dae47fbbf237c5d6dcbf345 0.600000000000 1438389 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": 978374, "vin": [ { "gen": { "height": 978364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63128ed99997aeefbed31a0d73d04fe9b61d61668dae47fbbf237c5d6dcbf345" } } ], "extra": [ 1, 205, 221, 50, 151, 203, 133, 244, 62, 144, 156, 166, 59, 249, 16, 254, 222, 140, 202, 78, 251, 78, 3, 37, 218, 46, 128, 85, 100, 41, 99, 51, 195, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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