Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973dc15ad438c369c2602403d244d6813536803796bc0c636b7e3cff71fd7250

Tx prefix hash: f183f9a0ab0d66a175ff5ade31a3601f20ac89544495fec588131a76d6f1ca02
Tx public key: 49669f12f3e187f7d80b373af7c99302f850cff2be25b11c3f03bbb5e5347dcb
Timestamp: 1698602384 Timestamp [UCT]: 2023-10-29 17:59:44 Age [y:d:h:m:s]: 01:094:18:08:34
Block: 880379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328677 RingCT/type: yes/0
Extra: 0149669f12f3e187f7d80b373af7c99302f850cff2be25b11c3f03bbb5e5347dcb021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.742914650000 dcy

stealth address amount amount idx
00: 7ccabdc23d0aeb612619ae740f43914fd897e502049953d381206dd9ed61974c 0.742914650000 1335935 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": 880389, "vin": [ { "gen": { "height": 880379 } } ], "vout": [ { "amount": 742914650, "target": { "key": "7ccabdc23d0aeb612619ae740f43914fd897e502049953d381206dd9ed61974c" } } ], "extra": [ 1, 73, 102, 159, 18, 243, 225, 135, 247, 216, 11, 55, 58, 247, 201, 147, 2, 248, 80, 207, 242, 190, 37, 177, 28, 63, 3, 187, 181, 229, 52, 125, 203, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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