Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3fa33b0d3f90b890e83762a913b95f65535f915d864298982259c9bc674597

Tx prefix hash: c97e0b0b9ccad71ef75c3ff8d8c6ea204fa36c8f76eddd908e67b918ba2cbf92
Tx public key: 871db4a618f867a5761047e3d934c0f64f2e34d6aaed95e5e83bd450c1d0b852
Timestamp: 1733333421 Timestamp [UCT]: 2024-12-04 17:30:21 Age [y:d:h:m:s]: 00:102:18:01:11
Block: 1167994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73254 RingCT/type: yes/0
Extra: 01871db4a618f867a5761047e3d934c0f64f2e34d6aaed95e5e83bd450c1d0b8520211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86206e9e742f71b3649ec8d9c743f33a7230cf716febb6f869e43a95b66d9a38 0.600000000000 1653699 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": 1168004, "vin": [ { "gen": { "height": 1167994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86206e9e742f71b3649ec8d9c743f33a7230cf716febb6f869e43a95b66d9a38" } } ], "extra": [ 1, 135, 29, 180, 166, 24, 248, 103, 165, 118, 16, 71, 227, 217, 52, 192, 246, 79, 46, 52, 214, 170, 237, 149, 229, 232, 59, 212, 80, 193, 208, 184, 82, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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