Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93907997f6aae70da6fd52470fddf33f2f730d6a8ba6250ad1e18450036f7049

Tx prefix hash: 58221e424d03d0498e8a469138418757886f5fba3a7b53f73fc78b6804bebdf5
Tx public key: 8de2a22683ef3b2ce4e8b4adfd5a3f69b53bac43698d5cb3a992c50f6b6e0991
Timestamp: 1756041504 Timestamp [UCT]: 2025-08-24 13:18:24 Age [y:d:h:m:s]: 00:094:01:52:04
Block: 1353441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67175 RingCT/type: yes/0
Extra: 018de2a22683ef3b2ce4e8b4adfd5a3f69b53bac43698d5cb3a992c50f6b6e09910211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9eb83ff31d8282d13d8ccf59540c6f1468e3dd97539e7aab4c4aa5f0ea220ee 0.600000000000 1841416 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": 1353451, "vin": [ { "gen": { "height": 1353441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9eb83ff31d8282d13d8ccf59540c6f1468e3dd97539e7aab4c4aa5f0ea220ee" } } ], "extra": [ 1, 141, 226, 162, 38, 131, 239, 59, 44, 228, 232, 180, 173, 253, 90, 63, 105, 181, 59, 172, 67, 105, 141, 92, 179, 169, 146, 197, 15, 107, 110, 9, 145, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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