← previous blocknext block →recent activity
Analyzing
Block #89,681,834
17 transactions · 15 stateful · 2026-07-23 16:42:39 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,681,834 · 17 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
2w04w15w27w38w09w110w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c2fc330…0091
0x34b655…2a6f
6 touches
3 conflicts
0x1da947c4…f74e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x8743e1ba…8331
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: Perpl
3 conflicts on slot 0x9c2fc33042…7d0091
Audit this contract →
← previous block·next block →recent activity