Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae6c0be2eec9edd7741ac5011256794c7b944e09505cd694b468b34ad4c6fd96

Tx prefix hash: 6e6af19b9083e2807b2aedb06401f98f4639ea47bba3f859c8dcd528fc6c8ed1
Tx public key: ec076366487a44cf048796ae11a8016ff99322e8f3ecf7e9a5bf4a659fc136d9
Timestamp: 1640290389 Timestamp [UCT]: 2021-12-23 20:13:09 Age [y:d:h:m:s]: 03:014:12:17:20
Block: 401993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 789351 RingCT/type: yes/0
Extra: 01ec076366487a44cf048796ae11a8016ff99322e8f3ecf7e9a5bf4a659fc136d902110000000237cb3088000000000000000000

1 output(s) for total of 28.577923167000 dcy

stealth address amount amount idx
00: 02dc03f776de5863ad8e001f8c9335f8fb73af1f89403946908237067d60135e 28.577923167000 801668 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": 402003, "vin": [ { "gen": { "height": 401993 } } ], "vout": [ { "amount": 28577923167, "target": { "key": "02dc03f776de5863ad8e001f8c9335f8fb73af1f89403946908237067d60135e" } } ], "extra": [ 1, 236, 7, 99, 102, 72, 122, 68, 207, 4, 135, 150, 174, 17, 168, 1, 111, 249, 147, 34, 232, 243, 236, 247, 233, 165, 191, 74, 101, 159, 193, 54, 217, 2, 17, 0, 0, 0, 2, 55, 203, 48, 136, 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