← previous blocknext block →recent activity
Analyzing
Block #87,506,215
18 transactions · 15 stateful · 2026-07-13 14:52:30 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,506,215 · 18 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
1w02w19w010w112w213w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xe5056fd5…3827
0x34b655…2a6f
6 touches
3 conflicts
0xe5620d52…7ede
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x3e0b5510…7fa8
0x34b655…2a6f
4 touches
1 conflict
0x4dea7bb6…6f63
0x34b655…2a6f
4 touches
1 conflict
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity