← previous blocknext block →recent activity
Analyzing
Block #87,503,452
31 transactions · 22 stateful · 2026-07-13 14:33:58 UTC
Parallelism
87/100
Blocked
50%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,503,452 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w111w012w115w116w218w019w021w222w123w324w125w229w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x22f5b72a…22e0
0x34b655…2a6f
4 touches
1 conflict
0x2eb2f58d…cc27
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x3cab3503…ea79
0x34b655…2a6f
4 touches
1 conflict
0x65af9c7d…9577
0x34b655…2a6f
4 touches
1 conflict
0x7cb1d883…dc23
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity