Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667baa601d2cac3a4d1ca833ee40911d1e75aa1cc35be90aced77737a391492e

Tx prefix hash: 64a86c53eab865d339385db70a32149a37398aaa9585768b62c768124894eace
Tx public key: 9f0e24dc8e7eb299e7659a1e8f996f9ae6a8c99b1aed6f77ca1b974097d697cd
Timestamp: 1760423362 Timestamp [UCT]: 2025-10-14 06:29:22 Age [y:d:h:m:s]: 00:107:21:49:10
Block: 1389574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77075 RingCT/type: yes/0
Extra: 019f0e24dc8e7eb299e7659a1e8f996f9ae6a8c99b1aed6f77ca1b974097d697cd021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a523152ea318705bd9ff8cb692a848ab665535a5e4de7bafa75885ac00ac12b 0.600000000000 1877803 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": 1389584, "vin": [ { "gen": { "height": 1389574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a523152ea318705bd9ff8cb692a848ab665535a5e4de7bafa75885ac00ac12b" } } ], "extra": [ 1, 159, 14, 36, 220, 142, 126, 178, 153, 231, 101, 154, 30, 143, 153, 111, 154, 230, 168, 201, 155, 26, 237, 111, 119, 202, 27, 151, 64, 151, 214, 151, 205, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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