← previous blocknext block →recent activity
Analyzing
Block #88,344,211
16 transactions · 16 stateful · 2026-07-17 12:18:45 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,344,211 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w19w210w311w112w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2f0b01…112a
0x34b655…2a6f
8 touches
6 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
6 touches
3 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5bdae4ca…5d23
0x34b655…2a6f
4 touches
1 conflict
0x5cc477b5…1cf3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0x5d2f0b01fb…19112a
Audit this contract →
← previous block·next block →recent activity