← previous blocknext block →recent activity
Analyzing
Block #87,703,875
51 transactions · 36 stateful · 2026-07-14 12:55:00 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
2.51
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,703,875 · 51 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w313w014w121w022w123w224w325w426w527w628w729w830w931w1032w1133w1234w1335w1442w447w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
12 touches
15 conflicts
0x5cf7c7d2…9640
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
12 touches
15 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
12 touches
15 conflicts
0xcfaa395f…5b1c
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity