Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ac146b3d42203a54085e455b7a733aed804adf04239764a4dc50b83f7aa5abe

Tx prefix hash: 8b45a080b5fe5a81b3875687914045357666b1dd08b97a38ec43a639d00d5f4c
Tx public key: eebea5afa29217f4edcfec7fe76b7e689285ae3dfe702a8af3bd7a728e451ec8
Timestamp: 1729903096 Timestamp [UCT]: 2024-10-26 00:38:16 Age [y:d:h:m:s]: 00:088:12:30:55
Block: 1139627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63250 RingCT/type: yes/0
Extra: 01eebea5afa29217f4edcfec7fe76b7e689285ae3dfe702a8af3bd7a728e451ec802110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d485b350ce1616305aee741d416926187b8e45eacae0e476d45a0b5d24a8584 0.600000000000 1623414 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": 1139637, "vin": [ { "gen": { "height": 1139627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d485b350ce1616305aee741d416926187b8e45eacae0e476d45a0b5d24a8584" } } ], "extra": [ 1, 238, 190, 165, 175, 162, 146, 23, 244, 237, 207, 236, 127, 231, 107, 126, 104, 146, 133, 174, 61, 254, 112, 42, 138, 243, 189, 122, 114, 142, 69, 30, 200, 2, 17, 0, 0, 0, 12, 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