Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b607dfd03a63092df1b8d9570fdc697257b0cb0a00de394e3a1ac4a73b713e60

Tx prefix hash: 40c39d0df600fc281b54ef851cf6d804de1dbecc98b1237db6a6aa84eaa19db6
Tx public key: 5b8d0cf8f77cb1b809cb7a524b1feb3b9694a7fa1a7584598f13317f5130f4ed
Timestamp: 1657141849 Timestamp [UCT]: 2022-07-06 21:10:49 Age [y:d:h:m:s]: 02:180:20:08:30
Block: 538129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650601 RingCT/type: yes/0
Extra: 015b8d0cf8f77cb1b809cb7a524b1feb3b9694a7fa1a7584598f13317f5130f4ed0211000000204da16a3a000000000000000000

1 output(s) for total of 10.114755395000 dcy

stealth address amount amount idx
00: de736aefb50f19597a48264ba364d7fcad29a3622384315c7eb23518bf2dec44 10.114755395000 968092 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": 538139, "vin": [ { "gen": { "height": 538129 } } ], "vout": [ { "amount": 10114755395, "target": { "key": "de736aefb50f19597a48264ba364d7fcad29a3622384315c7eb23518bf2dec44" } } ], "extra": [ 1, 91, 141, 12, 248, 247, 124, 177, 184, 9, 203, 122, 82, 75, 31, 235, 59, 150, 148, 167, 250, 26, 117, 132, 89, 143, 19, 49, 127, 81, 48, 244, 237, 2, 17, 0, 0, 0, 32, 77, 161, 106, 58, 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