Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53f64655ee5b63b6abed96e5c132bd89831a80b0916fb2fc844676a114853cc3

Tx prefix hash: 656601a57f26f2b11ad43c623f89f6ea5e5bc9cfd340cd4054b08fa381c279de
Tx public key: 6bca28e728c2624d8b68facf14fb602f3fd74427dfa323887bf2a091e919ce39
Timestamp: 1700745479 Timestamp [UCT]: 2023-11-23 13:17:59 Age [y:d:h:m:s]: 01:057:05:58:44
Block: 897925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302280 RingCT/type: yes/0
Extra: 016bca28e728c2624d8b68facf14fb602f3fd74427dfa323887bf2a091e919ce390211000000024b8f5122000000000000000000

1 output(s) for total of 0.649832930000 dcy

stealth address amount amount idx
00: c22bf6b1e2ddc70806947118dc3aa578e1c1e0e5999524769d187ac3e99f32a7 0.649832930000 1354322 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": 897935, "vin": [ { "gen": { "height": 897925 } } ], "vout": [ { "amount": 649832930, "target": { "key": "c22bf6b1e2ddc70806947118dc3aa578e1c1e0e5999524769d187ac3e99f32a7" } } ], "extra": [ 1, 107, 202, 40, 231, 40, 194, 98, 77, 139, 104, 250, 207, 20, 251, 96, 47, 63, 215, 68, 39, 223, 163, 35, 136, 123, 242, 160, 145, 233, 25, 206, 57, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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