Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63e00c27540113f8c4ca474ce5e48f873221bcddd06737963fad2502d3b50a3

Tx prefix hash: b627d81df6308bbb42f6ffc021363bb8f8a2040a5c4512f5424080e4b0a3ede8
Tx public key: 62fda7fe2182fecfc32aa43a4e858f78b2f53e7b63668fc7e62429179e33a528
Timestamp: 1711288532 Timestamp [UCT]: 2024-03-24 13:55:32 Age [y:d:h:m:s]: 00:290:15:32:30
Block: 985356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208034 RingCT/type: yes/0
Extra: 0162fda7fe2182fecfc32aa43a4e858f78b2f53e7b63668fc7e62429179e33a52802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7077b58a6ec13d9369002f03d8598d4ec19ac163c11baffb9b1085b8c97c162 0.600000000000 1445565 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": 985366, "vin": [ { "gen": { "height": 985356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7077b58a6ec13d9369002f03d8598d4ec19ac163c11baffb9b1085b8c97c162" } } ], "extra": [ 1, 98, 253, 167, 254, 33, 130, 254, 207, 195, 42, 164, 58, 78, 133, 143, 120, 178, 245, 62, 123, 99, 102, 143, 199, 230, 36, 41, 23, 158, 51, 165, 40, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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