Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f2fca1efd8486da3053f82924854daef20d7b0603cbcedc63c3e7f3146eb4b

Tx prefix hash: f6f346ca98dd58f5e4cb48cd9879437abaf9b6b6b3c3617d20f3e5646cafa66f
Tx public key: 71e68f26b82458f290135288e39f7ac189f57d31e4edd1be0ca4abab6f2c0fa5
Timestamp: 1762393044 Timestamp [UCT]: 2025-11-06 01:37:24 Age [y:d:h:m:s]: 00:048:06:55:58
Block: 1405879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34579 RingCT/type: yes/0
Extra: 0171e68f26b82458f290135288e39f7ac189f57d31e4edd1be0ca4abab6f2c0fa502110000000bdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe4aac33f99b8d7f4031ba99035d2ca559c9f97332e91399a1abcf069d78dc14 0.600000000000 1894260 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": 1405889, "vin": [ { "gen": { "height": 1405879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe4aac33f99b8d7f4031ba99035d2ca559c9f97332e91399a1abcf069d78dc14" } } ], "extra": [ 1, 113, 230, 143, 38, 184, 36, 88, 242, 144, 19, 82, 136, 227, 159, 122, 193, 137, 245, 125, 49, 228, 237, 209, 190, 12, 164, 171, 171, 111, 44, 15, 165, 2, 17, 0, 0, 0, 11, 223, 90, 36, 122, 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