Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d767908db445003a049a66ea5de92e6a34e9319c941d789fe091ae85366bc17e

Tx prefix hash: eee5a46bd0da52e3b1102d39c7f6bff2f898fcedfde592a357b6c9c4d8ca4e3a
Tx public key: f2983c108fa932177ed3b6b9640c283314c108e0d7361c9994e80e5ac03ef33e
Timestamp: 1579576389 Timestamp [UCT]: 2020-01-21 03:13:09 Age [y:d:h:m:s]: 04:290:17:56:11
Block: 49846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097488 RingCT/type: yes/0
Extra: 01f2983c108fa932177ed3b6b9640c283314c108e0d7361c9994e80e5ac03ef33e021100000003391a8d0e000000000000000000

1 output(s) for total of 419.642019091000 dcy

stealth address amount amount idx
00: 2260b01b15ba76a8274849bb024e2a6670bb700026465fed1f07b47107984db7 419.642019091000 92556 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": 49856, "vin": [ { "gen": { "height": 49846 } } ], "vout": [ { "amount": 419642019091, "target": { "key": "2260b01b15ba76a8274849bb024e2a6670bb700026465fed1f07b47107984db7" } } ], "extra": [ 1, 242, 152, 60, 16, 143, 169, 50, 23, 126, 211, 182, 185, 100, 12, 40, 51, 20, 193, 8, 224, 215, 54, 28, 153, 148, 232, 14, 90, 192, 62, 243, 62, 2, 17, 0, 0, 0, 3, 57, 26, 141, 14, 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