Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49822dfe563ee1db74a133866c335679bf9c6bbcf1c743f33775a2e6c3a74339

Tx prefix hash: aa5a4ab6d6092e8a8149d01ae10b3b8f2673dc4f7c19d4114d4b70934e3c29fd
Tx public key: 6b3c0bd039c02fe2976834cb5ff2608dfb3b2f1672f0e029ad95787fcc7d0e9c
Timestamp: 1748056386 Timestamp [UCT]: 2025-05-24 03:13:06 Age [y:d:h:m:s]: 00:180:04:48:23
Block: 1289625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126480 RingCT/type: yes/0
Extra: 016b3c0bd039c02fe2976834cb5ff2608dfb3b2f1672f0e029ad95787fcc7d0e9c0211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b25fe7c7bb8ce4fe9ee484597a066447ca7eccadbb7ea90af815b021d121a38a 0.600000000000 1777094 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": 1289635, "vin": [ { "gen": { "height": 1289625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b25fe7c7bb8ce4fe9ee484597a066447ca7eccadbb7ea90af815b021d121a38a" } } ], "extra": [ 1, 107, 60, 11, 208, 57, 192, 47, 226, 151, 104, 52, 203, 95, 242, 96, 141, 251, 59, 47, 22, 114, 240, 224, 41, 173, 149, 120, 127, 204, 125, 14, 156, 2, 17, 0, 0, 0, 1, 31, 144, 81, 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