Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54823fe5fd030e0f1ce1ab4da2ae4396710e22a54d72fc343fbcd68329d17e36

Tx prefix hash: d1cf96df7e671c3a4c6bd426d08d1adbd0c5fe802a693c4850b6a46230044235
Tx public key: 5fde383bdf1aaba09b42e49b4fefcbf6c554646b6aff93e75d35b1f7b28272ae
Timestamp: 1736326642 Timestamp [UCT]: 2025-01-08 08:57:22 Age [y:d:h:m:s]: 00:342:03:55:11
Block: 1192772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242093 RingCT/type: yes/0
Extra: 015fde383bdf1aaba09b42e49b4fefcbf6c554646b6aff93e75d35b1f7b28272ae021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 378d1ff13458ca9b7447b2e29d057aca15e21025cac89470392af515bd1680a2 0.600000000000 1679329 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": 1192782, "vin": [ { "gen": { "height": 1192772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "378d1ff13458ca9b7447b2e29d057aca15e21025cac89470392af515bd1680a2" } } ], "extra": [ 1, 95, 222, 56, 59, 223, 26, 171, 160, 155, 66, 228, 155, 79, 239, 203, 246, 197, 84, 100, 107, 106, 255, 147, 231, 93, 53, 177, 247, 178, 130, 114, 174, 2, 17, 0, 0, 0, 2, 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