Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42bfe7c516fa63fb700e20c1fafeff08f31dd8d246bc3b119dc55c4eced7de98

Tx prefix hash: 4e82071edb51da28a77a7e6330a725e430e9252f6b70b371b293cfd843d222ec
Tx public key: e0a9ed2187c845681abb04c5b69f855f8425ec3e9a0bc7eabaf9c359d22f3be5
Timestamp: 1630051283 Timestamp [UCT]: 2021-08-27 08:01:23 Age [y:d:h:m:s]: 03:191:20:01:06
Block: 321685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911455 RingCT/type: yes/0
Extra: 01e0a9ed2187c845681abb04c5b69f855f8425ec3e9a0bc7eabaf9c359d22f3be502110000000e0441b428000000000000000000

1 output(s) for total of 52.738104438000 dcy

stealth address amount amount idx
00: ea76f0fbcf34773753370207408ef14f3334b62ba0daafa875ebbcb486e7abd5 52.738104438000 667708 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": 321695, "vin": [ { "gen": { "height": 321685 } } ], "vout": [ { "amount": 52738104438, "target": { "key": "ea76f0fbcf34773753370207408ef14f3334b62ba0daafa875ebbcb486e7abd5" } } ], "extra": [ 1, 224, 169, 237, 33, 135, 200, 69, 104, 26, 187, 4, 197, 182, 159, 133, 95, 132, 37, 236, 62, 154, 11, 199, 234, 186, 249, 195, 89, 210, 47, 59, 229, 2, 17, 0, 0, 0, 14, 4, 65, 180, 40, 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