← previous blocknext block →recent activity
Analyzing
Block #87,620,687
31 transactions · 28 stateful · 2026-07-14 03:38:48 UTC
Parallelism
55/100
Blocked
61%
Avg conflicts / tx
2.71
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,620,687 · 31 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w211w312w413w514w615w717w818w919w1020w1124w129w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xc94a6349…4379
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0x19e9a11b…e981
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x34d95d94…3a16
0x34b655…2a6f
6 touches
3 conflicts
0x364289f7…f98a
0x34b655…2a6f
6 touches
3 conflicts
0x5a135c5e…c138
0x34b655…2a6f
6 touches
3 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity