Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb8bcdc8ca71c2dcf3490efdbbda1ccc47a44b986e40e4b9668c87969937b4a

Tx prefix hash: 860da07d2dc80dc935909209fbe336d9f88adc9b7781aaf9823dc1a3a328d5c0
Tx public key: aeff5a76628a50f41e9031386dd550567e0528704aa2ed58dccfe9994a4b5c8c
Timestamp: 1761235488 Timestamp [UCT]: 2025-10-23 16:04:48 Age [y:d:h:m:s]: 00:035:15:20:34
Block: 1396314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25501 RingCT/type: yes/0
Extra: 01aeff5a76628a50f41e9031386dd550567e0528704aa2ed58dccfe9994a4b5c8c021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94f6cf5a82601ec7ab67005f8d0ffc03fe66ff82f83a8bb739852b10720938e9 0.600000000000 1884599 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": 1396324, "vin": [ { "gen": { "height": 1396314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94f6cf5a82601ec7ab67005f8d0ffc03fe66ff82f83a8bb739852b10720938e9" } } ], "extra": [ 1, 174, 255, 90, 118, 98, 138, 80, 244, 30, 144, 49, 56, 109, 213, 80, 86, 126, 5, 40, 112, 74, 162, 237, 88, 220, 207, 233, 153, 74, 75, 92, 140, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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