← previous blocknext block →recent activity
Analyzing
Block #89,770,234
14 transactions · 13 stateful · 2026-07-24 00:08:52 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,770,234 · 14 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
2w04w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a332bb…0a80
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x15554b7b…e30e
0x34b655…2a6f
2 touches
0 conflicts
0x1b78ec69…0ce1
0x34b655…2a6f
2 touches
0 conflicts
0x2089dcc1…8f89
0x34b655…2a6f
2 touches
0 conflicts
0x2bb1123c…d9d1
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 0x13a332bb7d…080a80
Audit this contract →
← previous block·next block →recent activity