← previous blocknext block →recent activity
Analyzing
Block #87,304,932
19 transactions · 16 stateful · 2026-07-12 16:26:22 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,304,932 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w08w111w012w113w214w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3b76e3b6…6972
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5ff95106…7c15
0x34b655…2a6f
4 touches
1 conflict
0x5ff95106…7c16
0x34b655…2a6f
4 touches
1 conflict
0x6c7ca486…23f1
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
3 conflicts on slot 0x7e5ea60ab2…b0c4ab
Audit this contract →
← previous block·next block →recent activity