Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e189f7551185bec044d852727c5d6b92407cf4b09fbeb8d18f67ca036ffb126c

Tx prefix hash: 35bbdebe3decf8971d162f59dbbdfcf07d9df4093f6f4b2889ad2c6e47da7b74
Tx public key: fd526a9b9017d844ba3a73423b3ff14bafc76cf7a090273f50d3d16beb01d5f1
Timestamp: 1710588903 Timestamp [UCT]: 2024-03-16 11:35:03 Age [y:d:h:m:s]: 01:009:04:34:06
Block: 979553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267524 RingCT/type: yes/0
Extra: 01fd526a9b9017d844ba3a73423b3ff14bafc76cf7a090273f50d3d16beb01d5f10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d5192cd62b9b2005f9b55030003b7e2f39eee539801773790ef39078e2299d4 0.600000000000 1439590 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": 979563, "vin": [ { "gen": { "height": 979553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d5192cd62b9b2005f9b55030003b7e2f39eee539801773790ef39078e2299d4" } } ], "extra": [ 1, 253, 82, 106, 155, 144, 23, 216, 68, 186, 58, 115, 66, 59, 63, 241, 75, 175, 199, 108, 247, 160, 144, 39, 63, 80, 211, 209, 107, 235, 1, 213, 241, 2, 17, 0, 0, 0, 5, 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