Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daf949e018734f2b13fb6a013188cad2453a79df563b71275a96b09120d1dbf0

Tx prefix hash: ca27a2d44eb3ec83e4b2f2a5aab5beef67e50bd3564362499292fc4333515bbd
Tx public key: 13f0349ef345aacc56b0468730d8df74a4e52fd6c8cdfcf17f98f4c851ae13c2
Timestamp: 1720640758 Timestamp [UCT]: 2024-07-10 19:45:58 Age [y:d:h:m:s]: 00:273:11:01:11
Block: 1062872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195377 RingCT/type: yes/0
Extra: 0113f0349ef345aacc56b0468730d8df74a4e52fd6c8cdfcf17f98f4c851ae13c2021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75d18e97efb6cd7467bc2eaab756467e3194aac272911d338e78a823f3634ea7 0.600000000000 1533383 of 15

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": 1062882, "vin": [ { "gen": { "height": 1062872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75d18e97efb6cd7467bc2eaab756467e3194aac272911d338e78a823f3634ea7" } } ], "extra": [ 1, 19, 240, 52, 158, 243, 69, 170, 204, 86, 176, 70, 135, 48, 216, 223, 116, 164, 229, 47, 214, 200, 205, 252, 241, 127, 152, 244, 200, 81, 174, 19, 194, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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