← previous blocknext block →recent activity
Analyzing
Block #87,751,343
11 transactions · 10 stateful · 2026-07-14 18:12:46 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,751,343 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f384197…7b58
0x34b655…2a6f
4 touches
1 conflict
0xcb76b2ed…89a5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0802d0d8…dd0c
0x34b655…2a6f
2 touches
0 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfe038…c16c
0x34b655…2a6f
2 touches
0 conflicts
0x519e0fef…7303
0x34b655…2a6f
2 touches
0 conflicts
0x59dccbd8…2bf6
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
1 conflict on slot 0x1f38419714…3f7b58
Audit this contract →
← previous block·next block →recent activity