Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dac391071ade4241c37631bb4457f6a4ec6db58d28e11fe002835e613b4746f

Tx prefix hash: b7c8350f21133d0fb3aee5c05c07a768d94c2299131259d960c41aaa0b3141f2
Tx public key: 6e55312d3e4cb105880dcdf1ab96bf7264c79388bf8e3efed771dbb069d5e1cf
Timestamp: 1732314288 Timestamp [UCT]: 2024-11-22 22:24:48 Age [y:d:h:m:s]: 00:205:04:24:44
Block: 1159554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146411 RingCT/type: yes/0
Extra: 016e55312d3e4cb105880dcdf1ab96bf7264c79388bf8e3efed771dbb069d5e1cf021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da5f0a36fbf82ace07e4b3fe99dcb03c4de81c76370c66dc6fcb3df132e5e9e 0.600000000000 1645191 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": 1159564, "vin": [ { "gen": { "height": 1159554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da5f0a36fbf82ace07e4b3fe99dcb03c4de81c76370c66dc6fcb3df132e5e9e" } } ], "extra": [ 1, 110, 85, 49, 45, 62, 76, 177, 5, 136, 13, 205, 241, 171, 150, 191, 114, 100, 199, 147, 136, 191, 142, 62, 254, 215, 113, 219, 176, 105, 213, 225, 207, 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