Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 577697883d0f96379b3a6388149a97374de995acbb821bf5c44411e5a1034295

Tx prefix hash: 37df7ce364e8776ccf74b958025b6c91c83fe4a046f79fad4d922e40673d356e
Tx public key: f704c112f69b70b0cbbbac178e16bf06b79fd9e2221b3d260c7e77e9c78cc2c0
Timestamp: 1658630533 Timestamp [UCT]: 2022-07-24 02:42:13 Age [y:d:h:m:s]: 02:241:15:28:36
Block: 550388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 693893 RingCT/type: yes/0
Extra: 01f704c112f69b70b0cbbbac178e16bf06b79fd9e2221b3d260c7e77e9c78cc2c0021100000001aac913b7000000000000000000

1 output(s) for total of 9.211624173000 dcy

stealth address amount amount idx
00: 27e3657e162f800abe2d43553846a61d61e0a85f91c9398daa56eb7957c9798d 9.211624173000 981867 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": 550398, "vin": [ { "gen": { "height": 550388 } } ], "vout": [ { "amount": 9211624173, "target": { "key": "27e3657e162f800abe2d43553846a61d61e0a85f91c9398daa56eb7957c9798d" } } ], "extra": [ 1, 247, 4, 193, 18, 246, 155, 112, 176, 203, 187, 172, 23, 142, 22, 191, 6, 183, 159, 217, 226, 34, 27, 61, 38, 12, 126, 119, 233, 199, 140, 194, 192, 2, 17, 0, 0, 0, 1, 170, 201, 19, 183, 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