← previous blocknext block →recent activity
Analyzing
Block #87,641,127
13 transactions · 11 stateful · 2026-07-14 05:55:27 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,641,127 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7d99d945…e807
0x34b655…2a6f
6 touches
3 conflicts
0xe8706f47…bacf
0x34b655…2a6f
6 touches
3 conflicts
0x0a5a4598…01bc
0x34b655…2a6f
6 touches
3 conflicts
0x1febc2d0…0136
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2003d8cf…6836
0x34b655…2a6f
4 touches
1 conflict
0x13ed417e…a863
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity