← previous blocknext block →recent activity
Analyzing
Block #88,186,466
13 transactions · 12 stateful · 2026-07-16 18:44:01 UTC
Parallelism
46/100
Blocked
58%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,186,466 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w07w38w110w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0x77830e75…7f31
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfba400e9…635e
0x34b655…2a6f
6 touches
3 conflicts
0x335ffd3c…c132
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
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 0x2f4617255d…ea5ab2
Audit this contract →
← previous block·next block →recent activity