Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49a7e950018eb727e2595c910de9493165742a4f2a9924b9d4fcd3b945c28fc7

Tx prefix hash: 9516021739cd6a2301aadecb23218a37ef77fda5d7e91569655768f97b104e0a
Tx public key: f8d696ca8faf503adb6999dae96f75c4ac8235fae30bf7d671a2e341a3e43c17
Timestamp: 1749594010 Timestamp [UCT]: 2025-06-10 22:20:10 Age [y:d:h:m:s]: 00:162:09:41:19
Block: 1302353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113752 RingCT/type: yes/0
Extra: 01f8d696ca8faf503adb6999dae96f75c4ac8235fae30bf7d671a2e341a3e43c17021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23b531523e122dc614d4ba9e875ead0f6d0965a6af5745836967b213d1851bdb 0.600000000000 1789922 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": 1302363, "vin": [ { "gen": { "height": 1302353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23b531523e122dc614d4ba9e875ead0f6d0965a6af5745836967b213d1851bdb" } } ], "extra": [ 1, 248, 214, 150, 202, 143, 175, 80, 58, 219, 105, 153, 218, 233, 111, 117, 196, 172, 130, 53, 250, 227, 11, 247, 214, 113, 162, 227, 65, 163, 228, 60, 23, 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