← previous blocknext block →recent activity
Analyzing
Block #87,589,372
22 transactions · 19 stateful · 2026-07-14 00:09:24 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,589,372 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w29w310w411w512w413w519w020w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0xc2186704…5cc3
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
8 touches
6 conflicts
0x39c4bc47…ce30
0x34b655…2a6f
8 touches
6 conflicts
0xdb7c435f…f490
0x34b655…2a6f
6 touches
3 conflicts
0xad0c7701…1d83
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
6 conflicts on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity