Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dad840cbe05e06a53fe7407ccffce1009801acda32baea50e533b2af80be58af

Tx prefix hash: 121e17c33514b6f5fe7b3bbe94ea1afc674aa6af362f2e017530b1400e4bb96b
Tx public key: f6f826cc33f1cd78c5b9d4f2402feb56c25e636483ee5fcceb449afab5630dc2
Timestamp: 1750627299 Timestamp [UCT]: 2025-06-22 21:21:39 Age [y:d:h:m:s]: 00:149:12:16:38
Block: 1310691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104741 RingCT/type: yes/0
Extra: 01f6f826cc33f1cd78c5b9d4f2402feb56c25e636483ee5fcceb449afab5630dc2021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d73cc9929a5c80acf8efd8b92ac1c3a26bd648aa416abc4fe546c1aa0874cbb3 0.600000000000 1798314 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": 1310701, "vin": [ { "gen": { "height": 1310691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73cc9929a5c80acf8efd8b92ac1c3a26bd648aa416abc4fe546c1aa0874cbb3" } } ], "extra": [ 1, 246, 248, 38, 204, 51, 241, 205, 120, 197, 185, 212, 242, 64, 47, 235, 86, 194, 94, 99, 100, 131, 238, 95, 204, 235, 68, 154, 250, 181, 99, 13, 194, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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