← previous blocknext block →recent activity
Analyzing
Block #87,911,660
17 transactions · 17 stateful · 2026-07-15 12:05:06 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,911,660 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w08w19w211w312w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x4ab0fef9…caef
0x34b655…2a6f
8 touches
6 conflicts
0xebeee24a…ed8d
0x34b655…2a6f
8 touches
6 conflicts
0x0f6666e6…f280
0x34b655…2a6f
8 touches
6 conflicts
0x5a36d0c8…12e2
0x34b655…2a6f
6 touches
3 conflicts
0xf28cf8dc…b0ca
0x34b655…2a6f
6 touches
3 conflicts
0x00cd9338…40d2
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
10 conflicts on slot 0xa013ecc17b…017c8f
Audit this contract →
← previous block·next block →recent activity