← previous blocknext block →recent activity
Analyzing
Block #89,675,112
16 transactions · 11 stateful · 2026-07-23 16:08:36 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,675,112 · 16 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
2w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0c468e91…5fb3
0x34b655…2a6f
2 touches
0 conflicts
0x100acd29…3139
0x34b655…2a6f
2 touches
0 conflicts
0x13f8c55c…3061
0x34b655…2a6f
2 touches
0 conflicts
0x33d4fbe3…a782
0x34b655…2a6f
2 touches
0 conflicts
0x3ae2b530…45ee
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity