Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63adb7d77f6c2a8360a6a480a7e0a70e9fcad5c44f717474ecac8a389836dc9

Tx prefix hash: 934cf75ec679cb4bbfafbbe3b23071e375faddb419ae1ee51b03f38bc79adbb2
Tx public key: 0b5cb2dd85954fb309e3c4ded47c75f78e0cb01bd13ae4568b69863dfedb4764
Timestamp: 1751520656 Timestamp [UCT]: 2025-07-03 05:30:56 Age [y:d:h:m:s]: 00:173:21:29:45
Block: 1317727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122564 RingCT/type: yes/0
Extra: 010b5cb2dd85954fb309e3c4ded47c75f78e0cb01bd13ae4568b69863dfedb4764021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c797ab0e9a016a1638f473e499ba2ed00775442428dcaa2a4ed12857a8ff4456 0.600000000000 1805396 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": 1317737, "vin": [ { "gen": { "height": 1317727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c797ab0e9a016a1638f473e499ba2ed00775442428dcaa2a4ed12857a8ff4456" } } ], "extra": [ 1, 11, 92, 178, 221, 133, 149, 79, 179, 9, 227, 196, 222, 212, 124, 117, 247, 142, 12, 176, 27, 209, 58, 228, 86, 139, 105, 134, 61, 254, 219, 71, 100, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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