← previous blocknext block →recent activity
Analyzing
Block #86,851,420
22 transactions · 18 stateful · 2026-07-10 13:54:30 UTC
Parallelism
55/100
Blocked
72%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,851,420 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w211w112w213w314w415w518w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x4767551b…43c4
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity