Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0fb186c190d921916da3417360ce577935732de7ebff28211cfe8f6d166054

Tx prefix hash: 5bc938d59663ef31575fc332a91da746e04296a69fbd7b6cec63a901886c7dd6
Tx public key: 7e1e9fb5a307ebdb8b26471812681360212b054e151fd214d5920e5c31467429
Timestamp: 1583240160 Timestamp [UCT]: 2020-03-03 12:56:00 Age [y:d:h:m:s]: 04:297:13:01:12
Block: 75809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106758 RingCT/type: yes/0
Extra: 017e1e9fb5a307ebdb8b26471812681360212b054e151fd214d5920e5c314674290211000001a87adf42d3000000000000000000

1 output(s) for total of 344.202570473000 dcy

stealth address amount amount idx
00: 9be92115f10c1b92c35f115051bf127f3f87a1296126549ebde5c6f89c161db3 344.202570473000 139784 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": 75819, "vin": [ { "gen": { "height": 75809 } } ], "vout": [ { "amount": 344202570473, "target": { "key": "9be92115f10c1b92c35f115051bf127f3f87a1296126549ebde5c6f89c161db3" } } ], "extra": [ 1, 126, 30, 159, 181, 163, 7, 235, 219, 139, 38, 71, 24, 18, 104, 19, 96, 33, 43, 5, 78, 21, 31, 210, 20, 213, 146, 14, 92, 49, 70, 116, 41, 2, 17, 0, 0, 1, 168, 122, 223, 66, 211, 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