Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe0210efcfed4a9b39022b128bf6840012c6569dfe509c144297c8d68040241

Tx prefix hash: 10947c85ed727c3082174052d6b93ef9af16b1422130a7db021fd13d9c8381ee
Tx public key: ae16cb39df7dfecf776703c5a6f2de330922424162a789e492599511ce2d0f58
Timestamp: 1705435190 Timestamp [UCT]: 2024-01-16 19:59:50 Age [y:d:h:m:s]: 01:084:07:46:34
Block: 936791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321369 RingCT/type: yes/0
Extra: 01ae16cb39df7dfecf776703c5a6f2de330922424162a789e492599511ce2d0f580211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bfb7b2ce6b4e10502e2a3ac60e3cc431b6f5cd193c810d8e8e73248c177c033 0.600000000000 1394831 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": 936801, "vin": [ { "gen": { "height": 936791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bfb7b2ce6b4e10502e2a3ac60e3cc431b6f5cd193c810d8e8e73248c177c033" } } ], "extra": [ 1, 174, 22, 203, 57, 223, 125, 254, 207, 119, 103, 3, 197, 166, 242, 222, 51, 9, 34, 66, 65, 98, 167, 137, 228, 146, 89, 149, 17, 206, 45, 15, 88, 2, 17, 0, 0, 0, 4, 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