Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b11758406f4b2696ffae80086777e21fe97834e01365379c2c34f423556d83

Tx prefix hash: 31ca1941d0cfd385c374cc283a4f70ce71376a01e782005ffd841f0ad5f9e3ff
Tx public key: b98ef4e5abb3c9dd5a262e1784c136b077da6db03653d75e093cbd3f693ff8e1
Timestamp: 1732934774 Timestamp [UCT]: 2024-11-30 02:46:14 Age [y:d:h:m:s]: 00:122:23:34:47
Block: 1164694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87685 RingCT/type: yes/0
Extra: 01b98ef4e5abb3c9dd5a262e1784c136b077da6db03653d75e093cbd3f693ff8e1021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb454f3cf404a9cb7692b763e8a8d6bee0c4a631ed57e73001be1ae2653bff5 0.600000000000 1650367 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": 1164704, "vin": [ { "gen": { "height": 1164694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb454f3cf404a9cb7692b763e8a8d6bee0c4a631ed57e73001be1ae2653bff5" } } ], "extra": [ 1, 185, 142, 244, 229, 171, 179, 201, 221, 90, 38, 46, 23, 132, 193, 54, 176, 119, 218, 109, 176, 54, 83, 215, 94, 9, 60, 189, 63, 105, 63, 248, 225, 2, 17, 0, 0, 0, 5, 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