Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc04f3401a13383ff234ac165da330e335cd66e966a80236eb0f8ade8ce50d2

Tx prefix hash: 2200c93ef48dc67f61f39ce5201d40b30b28dbc4059dc0a80f7d007d9f8569d3
Tx public key: fff8086a8845e2b9496208803f247fe40eb7b5e6c5a24f09d65d885eecf3c5e2
Timestamp: 1704024907 Timestamp [UCT]: 2023-12-31 12:15:07 Age [y:d:h:m:s]: 01:094:12:21:28
Block: 925106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328667 RingCT/type: yes/0
Extra: 01fff8086a8845e2b9496208803f247fe40eb7b5e6c5a24f09d65d885eecf3c5e20211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e266792314c34ac07d2cd735dbd271ba5f2a285f7d0ee9dc681bfab000a38c0 0.600000000000 1382866 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": 925116, "vin": [ { "gen": { "height": 925106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e266792314c34ac07d2cd735dbd271ba5f2a285f7d0ee9dc681bfab000a38c0" } } ], "extra": [ 1, 255, 248, 8, 106, 136, 69, 226, 185, 73, 98, 8, 128, 63, 36, 127, 228, 14, 183, 181, 230, 197, 162, 79, 9, 214, 93, 136, 94, 236, 243, 197, 226, 2, 17, 0, 0, 0, 7, 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