← previous blocknext block →recent activity
Analyzing
Block #88,136,792
15 transactions · 13 stateful · 2026-07-16 13:10:57 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,136,792 · 15 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
1w02w04w05w16w27w38w19w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c429f11…0652
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x83fcbad4…dadd
0x34b655…2a6f
6 touches
3 conflicts
0x0a6ba3b4…2123
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x29856edf…841b
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x44fb0f8a…b7c3
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 0x2c429f119e…6d0652
Audit this contract →
← previous block·next block →recent activity