Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9da60bd4f4de9f7a80341d077a11830d0a7562caf46cf9d85c0e64f568db639

Tx prefix hash: 6d7aa4453e082322affd2b84d0253b8ff8fb81d226ad2ad448b5feb040ba812e
Tx public key: 7b819d3da19270591e648b8bc331397612377f3337c8037ce84bdef9bfebd8ed
Timestamp: 1582405076 Timestamp [UCT]: 2020-02-22 20:57:56 Age [y:d:h:m:s]: 04:278:03:43:27
Block: 70424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091337 RingCT/type: yes/0
Extra: 017b819d3da19270591e648b8bc331397612377f3337c8037ce84bdef9bfebd8ed0211000000044943cd9f000000000000000000

1 output(s) for total of 358.638456426000 dcy

stealth address amount amount idx
00: 8335b67c53ff1820c5fa8ef0ef43068aa3d73b4c7213baab693f0a9a25cfb469 358.638456426000 130130 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": 70434, "vin": [ { "gen": { "height": 70424 } } ], "vout": [ { "amount": 358638456426, "target": { "key": "8335b67c53ff1820c5fa8ef0ef43068aa3d73b4c7213baab693f0a9a25cfb469" } } ], "extra": [ 1, 123, 129, 157, 61, 161, 146, 112, 89, 30, 100, 139, 139, 195, 49, 57, 118, 18, 55, 127, 51, 55, 200, 3, 124, 232, 75, 222, 249, 191, 235, 216, 237, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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