← previous blocknext block →recent activity
Analyzing
Block #86,987,283
10 transactions · 9 stateful · 2026-07-11 05:02:37 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,987,283 · 10 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
3w04w06w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a6e42c5…9438
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0xb3e53c5e…b99c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1d61ab3f…1516
0x34b655…2a6f
2 touches
0 conflicts
0x45877cba…0b50
0x34b655…2a6f
2 touches
0 conflicts
0x4d7e366b…7690
0x34b655…2a6f
2 touches
0 conflicts
0x4ff21e31…8ed4
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
3 conflicts on slot 0x6a6e42c571…c39438
Audit this contract →
← previous block·next block →recent activity