← previous blocknext block →recent activity
Analyzing
Block #86,957,746
15 transactions · 14 stateful · 2026-07-11 01:45:16 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,957,746 · 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
3w04w16w27w38w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0446875…2b96
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb9369a89…39a3
0x34b655…2a6f
4 touches
1 conflict
0xcf090a80…4536
0x34b655…2a6f
4 touches
1 conflict
0xe1826fe3…f9c9
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 0xb04468752d…352b96
Audit this contract →
← previous block·next block →recent activity