← previous blocknext block →recent activity
Analyzing
Block #87,498,861
43 transactions · 36 stateful · 2026-07-13 14:03:16 UTC
Parallelism
60/100
Blocked
69%
Avg conflicts / tx
2.56
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,498,861 · 43 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w08w19w010w111w213w014w115w216w317w418w519w620w721w822w928w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0xfbabdfc2…09eb
0x34b655…2a6f
10 touches
10 conflicts
0x6a4868a5…367e
0x34b655…2a6f
10 touches
10 conflicts
0x13c5b486…d41e
0x34b655…2a6f
10 touches
10 conflicts
0x75586248…f0b4
0x34b655…2a6f
10 touches
10 conflicts
0x775a8ad3…8307
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity