Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14348a05c439ce5fca88e6f507c59bdb4b335bb0121c7f63e48843d2f864fcda

Tx prefix hash: cb339c8f5a2b7448a68d97c18e3d737d37f624e9f61eab81e09e86227da8e3ad
Tx public key: 83ca8c3a70d984a42352ea2414add51aab6e413df8b59137aaf7ad1c06950d1c
Timestamp: 1636639944 Timestamp [UCT]: 2021-11-11 14:12:24 Age [y:d:h:m:s]: 03:217:18:40:30
Block: 372145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 933974 RingCT/type: yes/0
Extra: 0183ca8c3a70d984a42352ea2414add51aab6e413df8b59137aaf7ad1c06950d1c02110000000c745f00f8000000000000000000

1 output(s) for total of 35.886369246000 dcy

stealth address amount amount idx
00: 2e1b060a55590882051a9144d0e310426804213e7318c75435b3d3e5c84f95c9 35.886369246000 753919 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": 372155, "vin": [ { "gen": { "height": 372145 } } ], "vout": [ { "amount": 35886369246, "target": { "key": "2e1b060a55590882051a9144d0e310426804213e7318c75435b3d3e5c84f95c9" } } ], "extra": [ 1, 131, 202, 140, 58, 112, 217, 132, 164, 35, 82, 234, 36, 20, 173, 213, 26, 171, 110, 65, 61, 248, 181, 145, 55, 170, 247, 173, 28, 6, 149, 13, 28, 2, 17, 0, 0, 0, 12, 116, 95, 0, 248, 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