← previous blocknext block →recent activity
Analyzing
Block #89,526,304
25 transactions · 22 stateful · 2026-07-23 00:03:58 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,526,304 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w110w211w312w421w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x344eea7a…886e
0x0a2fbf…29b1
10 touches
10 conflicts
0x55b4e430…44cb
0x754704…b603
10 touches
10 conflicts
0x344eea7a…8871
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x344eea7a…886d
0x0a2fbf…29b1
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x67bfbc55…7b2f
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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x344eea7ad7…62886e
Audit this contract →
← previous block·next block →recent activity