← previous blocknext block →recent activity
Analyzing
Block #87,911,626
21 transactions · 20 stateful · 2026-07-15 12:04:52 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,911,626 · 21 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
1w02w13w04w16w07w28w39w414w215w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe45167d0…c16c
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xfa2dadef…1654
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x671703d0…94b1
0x34b655…2a6f
6 touches
3 conflicts
0x6bf71f68…fd07
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
6 conflicts on slot 0xe45167d0d8…c2c16c
Audit this contract →
← previous block·next block →recent activity