Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 607651c1afcb6a3ab704725d491af6f7d7cf1269b9dfc0314911298aa5729284

Tx prefix hash: 75c5d1adcf25b5743c535b30cfee7c5b3d3be6ad72a1fb9b5a62109a602e5304
Tx public key: a923be9c6156d31179212d8c0ef1c6302be0697500201412ca6e1cd6c876c354
Timestamp: 1636910107 Timestamp [UCT]: 2021-11-14 17:15:07 Age [y:d:h:m:s]: 03:121:01:45:08
Block: 374235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 865084 RingCT/type: yes/0
Extra: 01a923be9c6156d31179212d8c0ef1c6302be0697500201412ca6e1cd6c876c35402110000001037cb3088000000000000000000

1 output(s) for total of 35.320071371000 dcy

stealth address amount amount idx
00: ba422a0be6a20d79c08d1a9a14e7a22d9aa9f0525319508a54a69e9f81e63858 35.320071371000 757577 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": 374245, "vin": [ { "gen": { "height": 374235 } } ], "vout": [ { "amount": 35320071371, "target": { "key": "ba422a0be6a20d79c08d1a9a14e7a22d9aa9f0525319508a54a69e9f81e63858" } } ], "extra": [ 1, 169, 35, 190, 156, 97, 86, 211, 17, 121, 33, 45, 140, 14, 241, 198, 48, 43, 224, 105, 117, 0, 32, 20, 18, 202, 110, 28, 214, 200, 118, 195, 84, 2, 17, 0, 0, 0, 16, 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