← previous blocknext block →recent activity
Analyzing
Block #86,908,750
19 transactions · 17 stateful · 2026-07-10 20:17:57 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,908,750 · 19 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
4w05w18w09w110w113w216w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d6062bd…88e0
0x34b655…2a6f
6 touches
3 conflicts
0x4bd41fd9…4194
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x78d79dcd…a930
0x34b655…2a6f
6 touches
3 conflicts
0x38f21580…d4c4
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0x88413c1a…7783
0x34b655…2a6f
4 touches
1 conflict
0x8ac8dc53…b753
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 0x8d6062bdd8…c188e0
Audit this contract →
← previous block·next block →recent activity