Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46776872badb1f4a6e7ea7e64948f929d5f120fdcbbb2946e3ee4a682a73595e

Tx prefix hash: 03e69ab9e733da0369a8788565014af49bf38bbac66ffa17746c6673dd5d603a
Tx public key: a1f6f7f643f932b823e3b2be06dc5ed0c900e0161d270e6aa3a823c8eff5bf16
Timestamp: 1645861051 Timestamp [UCT]: 2022-02-26 07:37:31 Age [y:d:h:m:s]: 03:078:00:11:21
Block: 446760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 835842 RingCT/type: yes/0
Extra: 01a1f6f7f643f932b823e3b2be06dc5ed0c900e0161d270e6aa3a823c8eff5bf16021100000002a272b9cb000000000000000000

1 output(s) for total of 20.309486578000 dcy

stealth address amount amount idx
00: 840be5ac1966ce91f44594cb857a87d47e71de3fb629f3473ca42ade5e1255cb 20.309486578000 860715 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": 446770, "vin": [ { "gen": { "height": 446760 } } ], "vout": [ { "amount": 20309486578, "target": { "key": "840be5ac1966ce91f44594cb857a87d47e71de3fb629f3473ca42ade5e1255cb" } } ], "extra": [ 1, 161, 246, 247, 246, 67, 249, 50, 184, 35, 227, 178, 190, 6, 220, 94, 208, 201, 0, 224, 22, 29, 39, 14, 106, 163, 168, 35, 200, 239, 245, 191, 22, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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