← previous blocknext block →recent activity
Analyzing
Block #88,159,131
14 transactions · 13 stateful · 2026-07-16 15:40:34 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,159,131 · 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
4w06w17w28w39w112w013w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06a48e8…d6d1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x239122db…dc81
0x34b655…2a6f
4 touches
1 conflict
0x471f2653…a639
0x34b655…2a6f
4 touches
1 conflict
0x87864c3c…06a8
0x34b655…2a6f
4 touches
1 conflict
0x87864c3c…06a9
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 0xb06a48e8ed…47d6d1
Audit this contract →
← previous block·next block →recent activity