← previous blocknext block →recent activity
Analyzing
Block #87,513,765
48 transactions · 35 stateful · 2026-07-13 15:43:02 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
2.06
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,513,765 · 48 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w011w119w020w121w222w323w424w525w626w727w828w929w1030w1131w1233w1346w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0x2fcd4130…b4a5
0xc8689a…ee79
10 touches
10 conflicts
0x0e76a52b…cfa3
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0x326f2a00…a2a6
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity