← previous blocknext block →recent activity
Analyzing
Block #87,870,644
18 transactions · 15 stateful · 2026-07-15 07:30:44 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,870,644 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w19w210w311w112w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe85e763f…3b25
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xac8a5059…fd42
0x34b655…2a6f
6 touches
3 conflicts
0x9a29b949…58de
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0xb8adb532…adf7
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity