← previous blocknext block →recent activity
Analyzing
Block #88,079,047
13 transactions · 11 stateful · 2026-07-16 06:44:38 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,079,047 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd708bac6…2e5d
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x2b2cf495…1c6f
0x34b655…2a6f
4 touches
1 conflict
0x216b66f8…bba8
0x34b655…2a6f
3 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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
3 conflicts on slot 0xd708bac619…892e5d
Audit this contract →
← previous block·next block →recent activity