Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 159b012eb6ab28eae377e6dcbd3336ae5200e5c9706b690614815abf5154ca41

Tx prefix hash: 6c0437357158dc72c0c6facda20af042cb9f12b8e97144f6f8d64476bc4cb428
Tx public key: 1ef04cf2684fadde29151d02839dc345b7491c3ec9b6ba64beafd120e1b84f25
Timestamp: 1577703896 Timestamp [UCT]: 2019-12-30 11:04:56 Age [y:d:h:m:s]: 05:109:20:57:58
Block: 34968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228317 RingCT/type: yes/0
Extra: 011ef04cf2684fadde29151d02839dc345b7491c3ec9b6ba64beafd120e1b84f25021100000030e39b962a000000000000000000

1 output(s) for total of 471.095866366000 dcy

stealth address amount amount idx
00: 0877ebea16f83fbc0ea31a455e1c55e8c0b198ce23e6176ce15afbdbba8de0d2 471.095866366000 58905 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": 34978, "vin": [ { "gen": { "height": 34968 } } ], "vout": [ { "amount": 471095866366, "target": { "key": "0877ebea16f83fbc0ea31a455e1c55e8c0b198ce23e6176ce15afbdbba8de0d2" } } ], "extra": [ 1, 30, 240, 76, 242, 104, 79, 173, 222, 41, 21, 29, 2, 131, 157, 195, 69, 183, 73, 28, 62, 201, 182, 186, 100, 190, 175, 209, 32, 225, 184, 79, 37, 2, 17, 0, 0, 0, 48, 227, 155, 150, 42, 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