Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a5709772832dfb3419a5e2eefd9a03f627e501176fbc5c2f4c9ce4133c9e3b

Tx prefix hash: 96c2453c7eec78e1b532f50c0a9444bbc73d3fcc2c6e13fdda1dce9da0747cfc
Tx public key: 56b77d5449be011a129edf3eec340fec3bc87120939c19cfb529f432d1617ac3
Timestamp: 1722404257 Timestamp [UCT]: 2024-07-31 05:37:37 Age [y:d:h:m:s]: 00:116:17:46:42
Block: 1077484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83528 RingCT/type: yes/0
Extra: 0156b77d5449be011a129edf3eec340fec3bc87120939c19cfb529f432d1617ac302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd0e9a711abe19906cbe0423c185350bad3c8a25b9539b55a9a563ccadad7fc7 0.600000000000 1550033 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": 1077494, "vin": [ { "gen": { "height": 1077484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd0e9a711abe19906cbe0423c185350bad3c8a25b9539b55a9a563ccadad7fc7" } } ], "extra": [ 1, 86, 183, 125, 84, 73, 190, 1, 26, 18, 158, 223, 62, 236, 52, 15, 236, 59, 200, 113, 32, 147, 156, 25, 207, 181, 41, 244, 50, 209, 97, 122, 195, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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