Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6e91fa6f1e4deb17f683d1eac7599b15c696058e934ab39cde055874fef4e3

Tx prefix hash: fa4ea0f24d5fd2c52b2392c653b53bd51366b395606fe43de9051116fa50ab9a
Tx public key: 59596bf5908c3c546f67d186f4927a878c1255f8778ee20192a1c26a13812b1f
Timestamp: 1751939810 Timestamp [UCT]: 2025-07-08 01:56:50 Age [y:d:h:m:s]: 00:185:15:28:57
Block: 1320994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131198 RingCT/type: yes/0
Extra: 0159596bf5908c3c546f67d186f4927a878c1255f8778ee20192a1c26a13812b1f021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6418135e4a811eef05d23903d61df330f1a791732aac6d875fef29c9dbe7543 0.600000000000 1808697 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": 1321004, "vin": [ { "gen": { "height": 1320994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6418135e4a811eef05d23903d61df330f1a791732aac6d875fef29c9dbe7543" } } ], "extra": [ 1, 89, 89, 107, 245, 144, 140, 60, 84, 111, 103, 209, 134, 244, 146, 122, 135, 140, 18, 85, 248, 119, 142, 226, 1, 146, 161, 194, 106, 19, 129, 43, 31, 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