Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8315e400f894ffa1daa9b2653609840f356cc5c7fc54c6a1aff9bc6157bfa117

Tx prefix hash: 2524530086bfebf2a74a8da685fb6d595278908a33fb3c22ea0d7ad426593550
Tx public key: c18bc037f21bdd70963b0749ebef6c073a32845c3b4a408f269ae123ccb44e00
Timestamp: 1699626213 Timestamp [UCT]: 2023-11-10 14:23:33 Age [y:d:h:m:s]: 01:151:13:09:36
Block: 888651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369500 RingCT/type: yes/0
Extra: 01c18bc037f21bdd70963b0749ebef6c073a32845c3b4a408f269ae123ccb44e00021100000005faf35c9c000000000000000000

1 output(s) for total of 0.697477722000 dcy

stealth address amount amount idx
00: 4781968e374c9e276e407665f2baa80c5909c61f8ea89dbad2bec4c561b456d8 0.697477722000 1344606 of 0

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": 888661, "vin": [ { "gen": { "height": 888651 } } ], "vout": [ { "amount": 697477722, "target": { "key": "4781968e374c9e276e407665f2baa80c5909c61f8ea89dbad2bec4c561b456d8" } } ], "extra": [ 1, 193, 139, 192, 55, 242, 27, 221, 112, 150, 59, 7, 73, 235, 239, 108, 7, 58, 50, 132, 92, 59, 74, 64, 143, 38, 154, 225, 35, 204, 180, 78, 0, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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