← previous blocknext block →recent activity
Analyzing
Block #87,303,857
12 transactions · 11 stateful · 2026-07-12 16:19:11 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,303,857 · 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
4w05w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0xf6366f16…1d91
0x34b655…2a6f
4 touches
1 conflict
0xfcb6731c…b151
0x34b655…2a6f
4 touches
1 conflict
0x05e83dc2…b7a0
0x34b655…2a6f
4 touches
1 conflict
0x22fc9794…6e93
0x34b655…2a6f
4 touches
1 conflict
0x3c4b8fbd…9354
0x34b655…2a6f
4 touches
1 conflict
0x6d24d9e6…400c
0x34b655…2a6f
4 touches
1 conflict
0x7624b9d6…59e6
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 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity