← previous blocknext block →recent activity
Analyzing
Block #86,686,600
19 transactions · 14 stateful · 2026-07-09 19:33:23 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,686,600 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db5666d…76f0
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0xff68ee4c…37e3
0x1111b3…4111
2 touches
0 conflicts
0x7fa718e1…80ea
0x34b655…2a6f
2 touches
0 conflicts
0x9706392a…02b0
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x8db5666d0a…ef76f0
Audit this contract →
← previous block·next block →recent activity