← previous blocknext block →recent activity
Analyzing
Block #87,919,666
22 transactions · 15 stateful · 2026-07-15 12:58:37 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,919,666 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w213w314w415w419w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x26cdc92a…04ba
0x34b655…2a6f
8 touches
6 conflicts
0x79287e09…898a
0x34b655…2a6f
8 touches
6 conflicts
0x03faff26…f533
0x34b655…2a6f
6 touches
3 conflicts
0x1321736a…43e3
0x34b655…2a6f
6 touches
3 conflicts
0xbbf74468…a54b
0x34b655…2a6f
6 touches
3 conflicts
0x165b3a0d…8987
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
15 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity