Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3efeb3252ad333b0727c7eb5b41f54f73c87c3146475cb2142d02005beacc226

Tx prefix hash: 48a910d951958df76c75c0d9ad328780ab040444f9e42a69eb789393ba183e2c
Tx public key: 3f6eee5a74da74a39800a7c2037ff642e6df70520e35f3a05bea51a2160351ff
Timestamp: 1726994133 Timestamp [UCT]: 2024-09-22 08:35:33 Age [y:d:h:m:s]: 00:109:10:05:35
Block: 1115542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78234 RingCT/type: yes/0
Extra: 013f6eee5a74da74a39800a7c2037ff642e6df70520e35f3a05bea51a2160351ff021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ded1333fb8837e4a0e8d35369dfea90ecc7418f2091e299a0f724d72d761c7dc 0.600000000000 1595711 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": 1115552, "vin": [ { "gen": { "height": 1115542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ded1333fb8837e4a0e8d35369dfea90ecc7418f2091e299a0f724d72d761c7dc" } } ], "extra": [ 1, 63, 110, 238, 90, 116, 218, 116, 163, 152, 0, 167, 194, 3, 127, 246, 66, 230, 223, 112, 82, 14, 53, 243, 160, 91, 234, 81, 162, 22, 3, 81, 255, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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