← previous blocknext block →recent activity
Analyzing
Block #87,065,150
18 transactions · 16 stateful · 2026-07-11 13:42:53 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,065,150 · 18 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
3w04w18w29w311w412w516w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0xfaef7662…f79b
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbbf74468…a54b
0x34b655…2a6f
6 touches
3 conflicts
0x5414d2b8…e8c9
0x34b655…2a6f
4 touches
1 conflict
0x1b374c44…96d9
0x34b655…2a6f
4 touches
1 conflict
0x5ed58b36…c5e5
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity