← previous blocknext block →recent activity
Analyzing
Block #86,989,955
14 transactions · 14 stateful · 2026-07-11 05:20:30 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,989,955 · 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
1w03w05w16w29w110w311w412w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf88a8b81…9197
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x34bd7c00…43fd
0x34b655…2a6f
4 touches
1 conflict
0x34bd7c00…43fe
0x34b655…2a6f
4 touches
1 conflict
0x42f3cd30…ad71
0x34b655…2a6f
4 touches
1 conflict
0x78984ebe…9e90
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity