← previous blocknext block →recent activity
Analyzing
Block #86,775,988
22 transactions · 15 stateful · 2026-07-10 05:30:23 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,775,988 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w411w015w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa84e1c73…0c49
0x34b655…2a6f
6 touches
3 conflicts
0x25f0d803…174f
0x34b655…2a6f
4 touches
1 conflict
0x4132a69b…f45e
0x34b655…2a6f
4 touches
1 conflict
0x5ad347dc…ff16
0x34b655…2a6f
4 touches
1 conflict
0x6f7775d0…a8b4
0x34b655…2a6f
4 touches
1 conflict
0x79e5df76…64ee
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity