Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5fc0a4b0ec19c9b3ef0e3e5fd00a0a6f1710972b6b9f0f6cec4413863edd401

Tx prefix hash: d5c94752e48ca5671c4632f798cbd9f68eac6cfdd889fb6473751eee57687917
Tx public key: a48ab22726f914d3302f4c153d1ac7973f16896a32be551bd4ca0ca63f9af989
Timestamp: 1699649041 Timestamp [UCT]: 2023-11-10 20:44:01 Age [y:d:h:m:s]: 01:139:21:06:36
Block: 888845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361147 RingCT/type: yes/0
Extra: 01a48ab22726f914d3302f4c153d1ac7973f16896a32be551bd4ca0ca63f9af98902110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.696446143000 dcy

stealth address amount amount idx
00: 74927b30a174b0393d56a729bb7a5c4af29754378127e5817eefd7309981d693 0.696446143000 1344806 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": 888855, "vin": [ { "gen": { "height": 888845 } } ], "vout": [ { "amount": 696446143, "target": { "key": "74927b30a174b0393d56a729bb7a5c4af29754378127e5817eefd7309981d693" } } ], "extra": [ 1, 164, 138, 178, 39, 38, 249, 20, 211, 48, 47, 76, 21, 61, 26, 199, 151, 63, 22, 137, 106, 50, 190, 85, 27, 212, 202, 12, 166, 63, 154, 249, 137, 2, 17, 0, 0, 0, 11, 250, 243, 92, 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