Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f963a662cd4a18bdee808423d5be7c751740cff14359e9ff0f395f4709e6aaf6

Tx prefix hash: 6f13c7d6f969026dc3c9caf4008f849bd223d54a831e6a8a2aeeeb10c58dc9d4
Tx public key: 8118a790e97c9703f287baebf7260ebb84b9475b20c7b117a3ab421d2c16443c
Timestamp: 1690577208 Timestamp [UCT]: 2023-07-28 20:46:48 Age [y:d:h:m:s]: 01:262:03:34:03
Block: 813896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448440 RingCT/type: yes/0
Extra: 018118a790e97c9703f287baebf7260ebb84b9475b20c7b117a3ab421d2c16443c02110000000a33af99f4000000000000000000

1 output(s) for total of 1.233743272000 dcy

stealth address amount amount idx
00: 630f13ce1664eaf439cdca0eb106815cf527aa6fe269ceb86db79cf24294b941 1.233743272000 1265645 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": 813906, "vin": [ { "gen": { "height": 813896 } } ], "vout": [ { "amount": 1233743272, "target": { "key": "630f13ce1664eaf439cdca0eb106815cf527aa6fe269ceb86db79cf24294b941" } } ], "extra": [ 1, 129, 24, 167, 144, 233, 124, 151, 3, 242, 135, 186, 235, 247, 38, 14, 187, 132, 185, 71, 91, 32, 199, 177, 23, 163, 171, 66, 29, 44, 22, 68, 60, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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