Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c2505ac7b89ed9b4bfe88e9d7e20b32a1cabea442d823e92ee7ee58e524c38

Tx prefix hash: 0e688ff188fe9b31b411926963a449e4665ede02472b8ffca9708e530748b67c
Tx public key: cc6c8db204f94012306e88d9dacc97eae6b23154494c736e5b8b8d2326e2607e
Timestamp: 1764635937 Timestamp [UCT]: 2025-12-02 00:38:57 Age [y:d:h:m:s]: 00:059:21:30:31
Block: 1424479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42697 RingCT/type: yes/0
Extra: 01cc6c8db204f94012306e88d9dacc97eae6b23154494c736e5b8b8d2326e2607e021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8df580d0729d2a5a1df608de1d9b9a20bea8374de5ddd92ddcd60b291885a1d2 0.600000000000 1913110 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": 1424489, "vin": [ { "gen": { "height": 1424479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8df580d0729d2a5a1df608de1d9b9a20bea8374de5ddd92ddcd60b291885a1d2" } } ], "extra": [ 1, 204, 108, 141, 178, 4, 249, 64, 18, 48, 110, 136, 217, 218, 204, 151, 234, 230, 178, 49, 84, 73, 76, 115, 110, 91, 139, 141, 35, 38, 226, 96, 126, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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