Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e02ab0bebf9a284d7b28894caf321821eee0109ab8f6c22d9d305cb2fc8be42

Tx prefix hash: 2a1c3eb16318d063ca0e4f830450471f451346edf94b963b54158269d70b8765
Tx public key: c51f9fa77dca0a3adc4befdd000652b6eee73eccfc53efecf97bdfe0a5571c37
Timestamp: 1721253346 Timestamp [UCT]: 2024-07-17 21:55:46 Age [y:d:h:m:s]: 00:260:18:11:36
Block: 1067959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186276 RingCT/type: yes/0
Extra: 01c51f9fa77dca0a3adc4befdd000652b6eee73eccfc53efecf97bdfe0a5571c3702110000001991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4a9306ea60b977bdccdc510cdb97ab06cbd8a48e66b1fb252c7cc1b09310515 0.600000000000 1538916 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": 1067969, "vin": [ { "gen": { "height": 1067959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4a9306ea60b977bdccdc510cdb97ab06cbd8a48e66b1fb252c7cc1b09310515" } } ], "extra": [ 1, 197, 31, 159, 167, 125, 202, 10, 58, 220, 75, 239, 221, 0, 6, 82, 182, 238, 231, 62, 204, 252, 83, 239, 236, 249, 123, 223, 224, 165, 87, 28, 55, 2, 17, 0, 0, 0, 25, 145, 225, 60, 4, 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