← previous blocknext block →recent activity
Analyzing
Block #86,850,055
40 transactions · 25 stateful · 2026-07-10 13:45:23 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,850,055 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w015w120w021w125w226w134w335w436w537w638w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0c53719e…0366
0x34b655…2a6f
4 touches
1 conflict
0x17de443f…90c1
0x34b655…2a6f
4 touches
1 conflict
0x46f259a2…2c7b
0x34b655…2a6f
4 touches
1 conflict
0x6c7b899c…70ff
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity