Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a200777606c9c4b35e87b40341b44de03a1063d3109d3425922b87e350aa18a2

Tx prefix hash: 0435c859ae878231cdf59b21c5f83735e6884eb15922eb9c8c339c737a9fe215
Tx public key: 660138db9c26194c67c724f638fc66d7333fb1ce1da37858aa9d42e40ea25d2a
Timestamp: 1704842589 Timestamp [UCT]: 2024-01-09 23:23:09 Age [y:d:h:m:s]: 01:109:13:26:11
Block: 931881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339430 RingCT/type: yes/0
Extra: 01660138db9c26194c67c724f638fc66d7333fb1ce1da37858aa9d42e40ea25d2a0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e68d331ac85d8cd5fead90c013ded94a0c53fd9f7d23d978abb59b7aae5a8ab8 0.600000000000 1389787 of 15

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": 931891, "vin": [ { "gen": { "height": 931881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e68d331ac85d8cd5fead90c013ded94a0c53fd9f7d23d978abb59b7aae5a8ab8" } } ], "extra": [ 1, 102, 1, 56, 219, 156, 38, 25, 76, 103, 199, 36, 246, 56, 252, 102, 215, 51, 63, 177, 206, 29, 163, 120, 88, 170, 157, 66, 228, 14, 162, 93, 42, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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