Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dae39f9b26c0773d8e3ef85324b487c39c1128170f41639f9af2d8993b848a5c

Tx prefix hash: 38e38c3df36e87bd1b3995e971a3633beae54007cef652a7da014cd0941791f7
Tx public key: 9d8bf2aab6190e7cad46894e9f75a7dbaf55fd3e5f40a940893d7afb01742c9d
Timestamp: 1580570526 Timestamp [UCT]: 2020-02-01 15:22:06 Age [y:d:h:m:s]: 05:006:00:26:09
Block: 56676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156062 RingCT/type: yes/0
Extra: 019d8bf2aab6190e7cad46894e9f75a7dbaf55fd3e5f40a940893d7afb01742c9d021100000005dcee4b4d000000000000000000

1 output(s) for total of 398.328211072000 dcy

stealth address amount amount idx
00: c69b8bf1ea399aa240ac1e5e405466dbcca1f3041d08e8e75c5814e26a0b8063 398.328211072000 104463 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": 56686, "vin": [ { "gen": { "height": 56676 } } ], "vout": [ { "amount": 398328211072, "target": { "key": "c69b8bf1ea399aa240ac1e5e405466dbcca1f3041d08e8e75c5814e26a0b8063" } } ], "extra": [ 1, 157, 139, 242, 170, 182, 25, 14, 124, 173, 70, 137, 78, 159, 117, 167, 219, 175, 85, 253, 62, 95, 64, 169, 64, 137, 61, 122, 251, 1, 116, 44, 157, 2, 17, 0, 0, 0, 5, 220, 238, 75, 77, 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