Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f535b21089ef2c89174e415e80d9e5cf2fb4b9c09a408e8250291bfb2e45665b

Tx prefix hash: 93513808a2cf49505112287125e201963df0060a883239907eaa6964c850d539
Tx public key: e4f665ad27dd3b0e0c36f335535a8b05c26e7ffc1fc5b378d14d94411b050700
Timestamp: 1765935434 Timestamp [UCT]: 2025-12-17 01:37:14 Age [y:d:h:m:s]: 00:043:08:19:21
Block: 1435243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30870 RingCT/type: yes/0
Extra: 01e4f665ad27dd3b0e0c36f335535a8b05c26e7ffc1fc5b378d14d94411b0507000211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8a854aee095af6b02e21b01c2d00f5e8f92bfc6b250d6b8452b9d10512a4bb1 0.600000000000 1924040 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": 1435253, "vin": [ { "gen": { "height": 1435243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8a854aee095af6b02e21b01c2d00f5e8f92bfc6b250d6b8452b9d10512a4bb1" } } ], "extra": [ 1, 228, 246, 101, 173, 39, 221, 59, 14, 12, 54, 243, 53, 83, 90, 139, 5, 194, 110, 127, 252, 31, 197, 179, 120, 209, 77, 148, 65, 27, 5, 7, 0, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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