Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fdeae1a4260d4b3ea18df159bc097c860a0aa524a79f942f4aefcd0653ceaf5

Tx prefix hash: 40593651e1e402f1794f30396b72f094172a2042a7c3c43f6a7a0a789ece4141
Tx public key: f614419799d43fe4342da68bb46b756682cae51a10e45223bbb6e8b283d8f7a3
Timestamp: 1755576965 Timestamp [UCT]: 2025-08-19 04:16:05 Age [y:d:h:m:s]: 00:094:19:42:27
Block: 1349624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67670 RingCT/type: yes/0
Extra: 01f614419799d43fe4342da68bb46b756682cae51a10e45223bbb6e8b283d8f7a3021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 968f91461e84b00a63bcb9abb910d9a8568dce477ec53a9d4674edf68ba91759 0.600000000000 1837557 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": 1349634, "vin": [ { "gen": { "height": 1349624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "968f91461e84b00a63bcb9abb910d9a8568dce477ec53a9d4674edf68ba91759" } } ], "extra": [ 1, 246, 20, 65, 151, 153, 212, 63, 228, 52, 45, 166, 139, 180, 107, 117, 102, 130, 202, 229, 26, 16, 228, 82, 35, 187, 182, 232, 178, 131, 216, 247, 163, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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