Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 461a3de19d12a234e261d1164e24b05bb7ca9a99aa8f3ec809deb159fe04cbd1

Tx prefix hash: a82902897b0f45de6bdf8d53881e72e0bff2029b7822d5b41bc94754023252d7
Tx public key: 114e669db3a32544074a0c1d64f447e09cde9a20a0eaf07a6c091e67cdd25ec3
Timestamp: 1750494147 Timestamp [UCT]: 2025-06-21 08:22:27 Age [y:d:h:m:s]: 00:153:15:01:54
Block: 1309627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107648 RingCT/type: yes/0
Extra: 01114e669db3a32544074a0c1d64f447e09cde9a20a0eaf07a6c091e67cdd25ec3021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 785d941065502f41bee890b29af93adaeb3aacafc50b9d01ae02d62e6458c329 0.600000000000 1797244 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": 1309637, "vin": [ { "gen": { "height": 1309627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "785d941065502f41bee890b29af93adaeb3aacafc50b9d01ae02d62e6458c329" } } ], "extra": [ 1, 17, 78, 102, 157, 179, 163, 37, 68, 7, 74, 12, 29, 100, 244, 71, 224, 156, 222, 154, 32, 160, 234, 240, 122, 108, 9, 30, 103, 205, 210, 94, 195, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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