← previous blocknext block →recent activity
Analyzing
Block #87,903,100
18 transactions · 18 stateful · 2026-07-15 11:07:51 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,903,100 · 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
4w07w08w19w210w311w412w114w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x30f3ece3…c237
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9f83113a…dcd8
0x34b655…2a6f
8 touches
6 conflicts
0xfc475c59…dd04
0x34b655…2a6f
6 touches
3 conflicts
0x350e5d8a…601f
0x34b655…2a6f
6 touches
3 conflicts
0x353a3a00…5e0a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity