Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a771934969e1ead9931073463c42ed032d32f16f89b393694e0bd975893a254

Tx prefix hash: c67bff20b6e446865b7c4f6b18d5ff2cac97111c87173d7d897f0d28648694fa
Tx public key: f83a98ac2a5b48462ae0e07e1b17d9950fd4eade3140e41a2eb0b531282401e5
Timestamp: 1752281166 Timestamp [UCT]: 2025-07-12 00:46:06 Age [y:d:h:m:s]: 00:132:14:17:20
Block: 1323573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93447 RingCT/type: yes/0
Extra: 01f83a98ac2a5b48462ae0e07e1b17d9950fd4eade3140e41a2eb0b531282401e50211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1727b8cc205a77c3e433d7e503b47666d1717c632e13bd9432d9adcda8ba93f3 0.600000000000 1811312 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": 1323583, "vin": [ { "gen": { "height": 1323573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1727b8cc205a77c3e433d7e503b47666d1717c632e13bd9432d9adcda8ba93f3" } } ], "extra": [ 1, 248, 58, 152, 172, 42, 91, 72, 70, 42, 224, 224, 126, 27, 23, 217, 149, 15, 212, 234, 222, 49, 64, 228, 26, 46, 176, 181, 49, 40, 36, 1, 229, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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