← previous blocknext block →recent activity
Analyzing
Block #87,783,761
12 transactions · 11 stateful · 2026-07-14 21:49:38 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,783,761 · 12 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
1w04w05w16w07w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb9b6ffc…3aab
0x34b655…2a6f
6 touches
3 conflicts
0xeb9b6ffc…3aac
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x671886b7…46fe
0x34b655…2a6f
4 touches
1 conflict
0x7a231537…deb4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xeb9b6ffc76…fe3aab
Audit this contract →
← previous block·next block →recent activity