Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f90b1b11bc77df9a7f19170fec80c78e6b7780c5b9e03b962364c3f12b9075

Tx prefix hash: f8f66addf4e0eb5bd59aa4654b3b6fec306f53517813b3334acfeef7a43fea65
Tx public key: 7c7b8ca40632096854b5230a3dc4d1f3ec775dc3e09614c289ed5084bc53c3eb
Timestamp: 1731746400 Timestamp [UCT]: 2024-11-16 08:40:00 Age [y:d:h:m:s]: 00:177:03:55:17
Block: 1154849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126460 RingCT/type: yes/0
Extra: 017c7b8ca40632096854b5230a3dc4d1f3ec775dc3e09614c289ed5084bc53c3eb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d76c4914fa0026afde685a6337399ef00d469e584c85d8c8b92a1f9cc503fc1 0.600000000000 1640462 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": 1154859, "vin": [ { "gen": { "height": 1154849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d76c4914fa0026afde685a6337399ef00d469e584c85d8c8b92a1f9cc503fc1" } } ], "extra": [ 1, 124, 123, 140, 164, 6, 50, 9, 104, 84, 181, 35, 10, 61, 196, 209, 243, 236, 119, 93, 195, 224, 150, 20, 194, 137, 237, 80, 132, 188, 83, 195, 235, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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