← previous blocknext block →recent activity
Analyzing
Block #87,643,768
20 transactions · 16 stateful · 2026-07-14 06:13:07 UTC
Parallelism
70/100
Blocked
31%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,643,768 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w214w315w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2f0c7a17…9360
0x34b655…2a6f
4 touches
1 conflict
0x2f0c7a17…9361
0x34b655…2a6f
4 touches
1 conflict
0x457cca76…23b0
0x34b655…2a6f
4 touches
1 conflict
0x5bb46f6c…7693
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
10 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity