← previous blocknext block →recent activity
Analyzing
Block #86,928,079
13 transactions · 11 stateful · 2026-07-10 22:27:04 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,928,079 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf66a16ae…0da8
0x34b655…2a6f
4 touches
1 conflict
0x94ab81a0…5e6b
0x34b655…2a6f
4 touches
1 conflict
0xa7626318…e265
0x34b655…2a6f
4 touches
1 conflict
0xae7513f7…1dd3
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a2
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity