Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b0bdfe019292fe1ce292e4e712a8ec7b42179b11e972ab6a47fb55f9ee9438f

Tx prefix hash: 2d238b64ce075e2ddb522474237dedf1c213a7b6328cc0dbadf9a7410f539d1c
Tx public key: 01a982d2a94aecb459fc3f38e25d4b1b6d0c7e330d3d2a31c71230ef988767c9
Timestamp: 1574753039 Timestamp [UCT]: 2019-11-26 07:23:59 Age [y:d:h:m:s]: 05:075:15:00:00
Block: 17724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196647 RingCT/type: yes/0
Extra: 0101a982d2a94aecb459fc3f38e25d4b1b6d0c7e330d3d2a31c71230ef988767c9021100000001f95225a5000000000000000000

1 output(s) for total of 536.134692352000 dcy

stealth address amount amount idx
00: 1a65dee1cd307a509d5cd17adb66e61e697806961b85ad61cbbd3eec416e4854 536.134692352000 26182 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": 17734, "vin": [ { "gen": { "height": 17724 } } ], "vout": [ { "amount": 536134692352, "target": { "key": "1a65dee1cd307a509d5cd17adb66e61e697806961b85ad61cbbd3eec416e4854" } } ], "extra": [ 1, 1, 169, 130, 210, 169, 74, 236, 180, 89, 252, 63, 56, 226, 93, 75, 27, 109, 12, 126, 51, 13, 61, 42, 49, 199, 18, 48, 239, 152, 135, 103, 201, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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