← previous blocknext block →recent activity
Analyzing
Block #86,988,848
20 transactions · 19 stateful · 2026-07-11 05:13:06 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,988,848 · 20 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
4w05w16w27w08w19w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe78cce7…101c
0x34b655…2a6f
6 touches
3 conflicts
0x31c77e11…2fd8
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x59ededb5…45c4
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8eef368f…aa21
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 0xbe78cce772…02101c
Audit this contract →
← previous block·next block →recent activity