← previous blocknext block →recent activity
Analyzing
Block #89,708,365
36 transactions · 35 stateful · 2026-07-23 18:56:25 UTC
Parallelism
58/100
Blocked
74%
Avg conflicts / tx
3.89
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,708,365 · 36 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w08w39w410w113w014w015w116w117w218w219w320w421w322w523w624w425w726w527w628w729w830w931w1032w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
30 touches
105 conflicts
0x92339d95…0800
0xb1c8ea…8888
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x8a7411d0…617c
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x0000a8fd…758888
105 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity