Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b93d26a48d7e91b11804d184becb60c1787b6490650da5f11ddeb4bbd703a86e

Tx prefix hash: 5727350238d7dba668f2cc6a684b5c148344ed74ae6fc545e46de3c447b0d496
Tx public key: 172eea8d226a867cdd59513f5347fff09f1f5fe3e686ff43a3ac719bac1c96d1
Timestamp: 1755536296 Timestamp [UCT]: 2025-08-18 16:58:16 Age [y:d:h:m:s]: 00:088:14:27:42
Block: 1349313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63190 RingCT/type: yes/0
Extra: 01172eea8d226a867cdd59513f5347fff09f1f5fe3e686ff43a3ac719bac1c96d1021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44c4fce82a1ba68b4a8dcf987a7a57bad066c329c8b49961f5f0109592c21edc 0.600000000000 1837244 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": 1349323, "vin": [ { "gen": { "height": 1349313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44c4fce82a1ba68b4a8dcf987a7a57bad066c329c8b49961f5f0109592c21edc" } } ], "extra": [ 1, 23, 46, 234, 141, 34, 106, 134, 124, 221, 89, 81, 63, 83, 71, 255, 240, 159, 31, 95, 227, 230, 134, 255, 67, 163, 172, 113, 155, 172, 28, 150, 209, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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