← previous blocknext block →recent activity
Analyzing
Block #86,905,221
13 transactions · 12 stateful · 2026-07-10 19:54:20 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,905,221 · 13 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
2w03w14w25w38w09w211w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7da56943…9753
0x34b655…2a6f
4 touches
1 conflict
0x8dfef5ae…9361
0x34b655…2a6f
4 touches
1 conflict
0x8f7038d3…3804
0x34b655…2a6f
4 touches
1 conflict
0x9138a113…0d5f
0x34b655…2a6f
4 touches
1 conflict
0x94b8e9d6…77d6
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 0xa08f40b255…099a93
Audit this contract →
← previous block·next block →recent activity