Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81de08ec064890792940f45a58de29eccf11ce369a36edeb7f39f6aa657c8aa8

Tx prefix hash: f97ab6fed658a8fa509130772a37ae0b515b29b85fe67d1b7f0e16666ebae2fb
Tx public key: c1aaac82a814edd42066c26c8c8ee38b87d50a42b01c0b540a669d0e12288b17
Timestamp: 1707899031 Timestamp [UCT]: 2024-02-14 08:23:51 Age [y:d:h:m:s]: 01:278:04:06:27
Block: 957220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457587 RingCT/type: yes/0
Extra: 01c1aaac82a814edd42066c26c8c8ee38b87d50a42b01c0b540a669d0e12288b170211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5704b01c7753bdb8653a07dae7bd58215215e5d95cce66f97832d2e525014f80 0.600000000000 1416536 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": 957230, "vin": [ { "gen": { "height": 957220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5704b01c7753bdb8653a07dae7bd58215215e5d95cce66f97832d2e525014f80" } } ], "extra": [ 1, 193, 170, 172, 130, 168, 20, 237, 212, 32, 102, 194, 108, 140, 142, 227, 139, 135, 213, 10, 66, 176, 28, 11, 84, 10, 102, 157, 14, 18, 40, 139, 23, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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