Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a34a545d672e0efb784c83bdab1cb5c7ed791394c288bdba759a8b728b62447

Tx prefix hash: dcece39eaa76be2d1459527b1b1075a6da6a57283836aa25cbbf91ce98562c48
Tx public key: aa7533cbb9e114bbcc941973f36559ea6a8386db3a5b18a382e5bc5509254918
Timestamp: 1700412929 Timestamp [UCT]: 2023-11-19 16:55:29 Age [y:d:h:m:s]: 01:141:18:50:32
Block: 895169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362515 RingCT/type: yes/0
Extra: 01aa7533cbb9e114bbcc941973f36559ea6a8386db3a5b18a382e5bc5509254918021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.663641431000 dcy

stealth address amount amount idx
00: 7be8377782fde9557b26bd8ad4a9cf3a5c8b318642b0ee1ffac6669e8e1aaf49 0.663641431000 1351392 of 0

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": 895179, "vin": [ { "gen": { "height": 895169 } } ], "vout": [ { "amount": 663641431, "target": { "key": "7be8377782fde9557b26bd8ad4a9cf3a5c8b318642b0ee1ffac6669e8e1aaf49" } } ], "extra": [ 1, 170, 117, 51, 203, 185, 225, 20, 187, 204, 148, 25, 115, 243, 101, 89, 234, 106, 131, 134, 219, 58, 91, 24, 163, 130, 229, 188, 85, 9, 37, 73, 24, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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