Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3938a7019f5158e93a56b5e8798310dd75274e949269f2b638c2218f9e2a10a

Tx prefix hash: bc8c1c7b5df5aced6b0fa838e902bf3b4c50672095c65fb87572029b13b82f05
Tx public key: 59c568c6158eaddeb840ee32f822b175a1815f1876ecf22aef088dd9db396b9d
Timestamp: 1753269378 Timestamp [UCT]: 2025-07-23 11:16:18 Age [y:d:h:m:s]: 00:115:17:14:47
Block: 1331606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81533 RingCT/type: yes/0
Extra: 0159c568c6158eaddeb840ee32f822b175a1815f1876ecf22aef088dd9db396b9d021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e58d17795e3b716551946f2528023bdd5b70a82a238a9228b18e5c68d1eec8c 0.600000000000 1819401 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": 1331616, "vin": [ { "gen": { "height": 1331606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e58d17795e3b716551946f2528023bdd5b70a82a238a9228b18e5c68d1eec8c" } } ], "extra": [ 1, 89, 197, 104, 198, 21, 142, 173, 222, 184, 64, 238, 50, 248, 34, 177, 117, 161, 129, 95, 24, 118, 236, 242, 42, 239, 8, 141, 217, 219, 57, 107, 157, 2, 17, 0, 0, 0, 1, 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