← previous blocknext block →recent activity
Analyzing
Block #88,081,224
14 transactions · 14 stateful · 2026-07-16 06:59:12 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,081,224 · 14 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
3w04w17w28w39w311w413w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5777bd87…71bd
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x123c223a…e742
0x34b655…2a6f
4 touches
1 conflict
0x255ba9f3…396d
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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 0x5777bd874f…7071bd
Audit this contract →
← previous block·next block →recent activity