← previous blocknext block →recent activity
Analyzing
Block #87,310,410
13 transactions · 9 stateful · 2026-07-12 17:02:59 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,310,410 · 13 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
7w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x680ca7d7…2df4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf45f2405…c8f9
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x8112774f…dba3
0x34b655…2a6f
4 touches
1 conflict
0x816d9631…9fa5
0x34b655…2a6f
4 touches
1 conflict
0x8e7e9235…01bb
0x34b655…2a6f
4 touches
1 conflict
0x8e7e9235…01bc
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 0x680ca7d7a6…292df4
Audit this contract →
← previous block·next block →recent activity