← previous blocknext block →recent activity
Analyzing
Block #86,788,778
15 transactions · 12 stateful · 2026-07-10 06:55:44 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,788,778 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w09w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6323c5ea…ce8a
0x34b655…2a6f
4 touches
1 conflict
0x87a24499…0acf
0x34b655…2a6f
4 touches
1 conflict
0xa243ce39…3ff4
0x34b655…2a6f
4 touches
1 conflict
0xb3d0943e…c6e7
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