Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1896d0bf14489a184808534f286679dec8f5cbb8e9585ae861b3120210fbb3b5

Tx prefix hash: 3cdb512295bcb0a8b39fae07c151064246e9e918cbdd3a0b0a5a8cc4a2b2f421
Tx public key: fc9e4c42207bf76037a3de9980e3de764141f0f1de2be331b25bbd7eb951e760
Timestamp: 1718640787 Timestamp [UCT]: 2024-06-17 16:13:07 Age [y:d:h:m:s]: 00:284:14:54:22
Block: 1046285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203385 RingCT/type: yes/0
Extra: 01fc9e4c42207bf76037a3de9980e3de764141f0f1de2be331b25bbd7eb951e76002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23251a6183e718a45007f33cba8eb03e5c8d1791a592e7fa1c17f337c7198705 0.600000000000 1516096 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": 1046295, "vin": [ { "gen": { "height": 1046285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23251a6183e718a45007f33cba8eb03e5c8d1791a592e7fa1c17f337c7198705" } } ], "extra": [ 1, 252, 158, 76, 66, 32, 123, 247, 96, 55, 163, 222, 153, 128, 227, 222, 118, 65, 65, 240, 241, 222, 43, 227, 49, 178, 91, 189, 126, 185, 81, 231, 96, 2, 17, 0, 0, 0, 1, 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