Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0239a725e15bee2fbb6e12bed290364e288d249700acecf7ac4084af9c3892fa

Tx prefix hash: e68817c618b803cffd35c1ce72e3b2c0d23332a7b6201a240cc604cdfebee2a7
Tx public key: 041a0ae8b4d2c20d3f1c3979a002547eb07aacc5563b8ccacf60601d8fb6ba8e
Timestamp: 1656004281 Timestamp [UCT]: 2022-06-23 17:11:21 Age [y:d:h:m:s]: 02:235:20:34:09
Block: 528766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689642 RingCT/type: yes/0
Extra: 01041a0ae8b4d2c20d3f1c3979a002547eb07aacc5563b8ccacf60601d8fb6ba8e0211000000015eb576c5000000000000000000

1 output(s) for total of 10.863728518000 dcy

stealth address amount amount idx
00: 85fb7e7e1b3e787a9f9f39a1054c41450a3dbc960819b8a74fee57e1f0bc3db9 10.863728518000 957625 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": 528776, "vin": [ { "gen": { "height": 528766 } } ], "vout": [ { "amount": 10863728518, "target": { "key": "85fb7e7e1b3e787a9f9f39a1054c41450a3dbc960819b8a74fee57e1f0bc3db9" } } ], "extra": [ 1, 4, 26, 10, 232, 180, 210, 194, 13, 63, 28, 57, 121, 160, 2, 84, 126, 176, 122, 172, 197, 86, 59, 140, 202, 207, 96, 96, 29, 143, 182, 186, 142, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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