← previous blocknext block →recent activity
Analyzing
Block #89,739,458
11 transactions · 10 stateful · 2026-07-23 21:33:24 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,739,458 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e158caa…c4cf
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xcd899d87…c031
0x34b655…2a6f
4 touches
1 conflict
0x063d0c38…f603
0x34b655…2a6f
2 touches
0 conflicts
0x19c4c02b…4566
0x34b655…2a6f
2 touches
0 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
2 touches
0 conflicts
0x36cab528…6e38
0x34b655…2a6f
2 touches
0 conflicts
0x4e2af3ce…caf3
0x34b655…2a6f
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0x0e158caa36…f0c4cf
Audit this contract →
← previous block·next block →recent activity