← previous blocknext block →recent activity
Analyzing
Block #88,139,010
11 transactions · 7 stateful · 2026-07-16 13:25:46 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,139,010 · 11 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
1w02w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x52a2ba74…f2f7
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7f7bbb0d…6f60
0x34b655…2a6f
4 touches
1 conflict
0x8ce19e5c…e818
0x34b655…2a6f
4 touches
1 conflict
0x9465204c…bf37
0x34b655…2a6f
4 touches
1 conflict
0xa9b8a24d…3277
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
1 conflict on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity