Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5af62366a83107f8cacfa7776f62bf3fffefba4816ca152f1a083a23513613d7

Tx prefix hash: 37b6374cec424eb5006beca6576a1ca26feee30242bce3900d967ea839bb88dc
Tx public key: 66b2f40b1c966c8bf94a8a995ef8464c860d95722e6cbed587c381e5330e211d
Timestamp: 1648891542 Timestamp [UCT]: 2022-04-02 09:25:42 Age [y:d:h:m:s]: 03:216:20:10:03
Block: 471538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933039 RingCT/type: yes/0
Extra: 0166b2f40b1c966c8bf94a8a995ef8464c860d95722e6cbed587c381e5330e211d0211000000022e6b1fd5000000000000000000

1 output(s) for total of 16.811215235000 dcy

stealth address amount amount idx
00: 4bd49e082b40d48d29544a58d3e00255ad72f259a3be34da1a3e7a35c2f7cc3c 16.811215235000 890890 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": 471548, "vin": [ { "gen": { "height": 471538 } } ], "vout": [ { "amount": 16811215235, "target": { "key": "4bd49e082b40d48d29544a58d3e00255ad72f259a3be34da1a3e7a35c2f7cc3c" } } ], "extra": [ 1, 102, 178, 244, 11, 28, 150, 108, 139, 249, 74, 138, 153, 94, 248, 70, 76, 134, 13, 149, 114, 46, 108, 190, 213, 135, 195, 129, 229, 51, 14, 33, 29, 2, 17, 0, 0, 0, 2, 46, 107, 31, 213, 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