Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a6bc851afce58b247322deb5c548615c3f32ef7f6e5b7492294f46d6693e249

Tx prefix hash: 26e4682b0b3d7466253947534ca2eff4aca9cebcf5f3a02a112c7bec8d75eedc
Tx public key: 5b021a23a72a5b8ec0855496ae0d6d6c14e56cfd8be46bbc7fad473c9cc95057
Timestamp: 1764973003 Timestamp [UCT]: 2025-12-05 22:16:43 Age [y:d:h:m:s]: 00:058:16:13:46
Block: 1427267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41845 RingCT/type: yes/0
Extra: 015b021a23a72a5b8ec0855496ae0d6d6c14e56cfd8be46bbc7fad473c9cc9505702110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b12dfaf499c0532b76f42a9b2e26d2fdbf702cebad784765467c8682844c2944 0.600000000000 1915968 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": 1427277, "vin": [ { "gen": { "height": 1427267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b12dfaf499c0532b76f42a9b2e26d2fdbf702cebad784765467c8682844c2944" } } ], "extra": [ 1, 91, 2, 26, 35, 167, 42, 91, 142, 192, 133, 84, 150, 174, 13, 109, 108, 20, 229, 108, 253, 139, 228, 107, 188, 127, 173, 71, 60, 156, 201, 80, 87, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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