← previous blocknext block →recent activity
Analyzing
Block #87,758,328
19 transactions · 18 stateful · 2026-07-14 18:59:27 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,758,328 · 19 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
6w07w08w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x4cee015b…1a5e
0x34b655…2a6f
6 touches
3 conflicts
0xccee5b8f…1a7d
0x34b655…2a6f
6 touches
3 conflicts
0xee28d8b5…bd37
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09d
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09c
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity