Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3abfddbd99d0c299aa6c5ac3201dce64fe3aad807d58c0e09f09dffe1ad805

Tx prefix hash: 0255eca98cb49061520b270a95fcf4f6bba697328aa97b2bf13dea8f783dfce0
Tx public key: 7f85f08b59fc6ce98f4f43b7c60f94cb07178d69dee4c0bb442da86b65d9ff18
Timestamp: 1720692282 Timestamp [UCT]: 2024-07-11 10:04:42 Age [y:d:h:m:s]: 01:131:17:42:21
Block: 1063305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352672 RingCT/type: yes/0
Extra: 017f85f08b59fc6ce98f4f43b7c60f94cb07178d69dee4c0bb442da86b65d9ff18021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce396d5d7aff801bf4962116a04ec398aca3c479c1bad2e406b6356838f00b8a 0.600000000000 1533820 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": 1063315, "vin": [ { "gen": { "height": 1063305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce396d5d7aff801bf4962116a04ec398aca3c479c1bad2e406b6356838f00b8a" } } ], "extra": [ 1, 127, 133, 240, 139, 89, 252, 108, 233, 143, 79, 67, 183, 198, 15, 148, 203, 7, 23, 141, 105, 222, 228, 192, 187, 68, 45, 168, 107, 101, 217, 255, 24, 2, 17, 0, 0, 0, 4, 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