← previous blocknext block →recent activity
Analyzing
Block #87,877,274
25 transactions · 19 stateful · 2026-07-15 08:15:04 UTC
Parallelism
72/100
Blocked
37%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,877,274 · 25 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
3w04w17w28w39w410w512w013w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0f6666e6…f280
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x974c36fe…1cd7
0x34b655…2a6f
6 touches
3 conflicts
0x322fb0e8…962d
0x34b655…2a6f
4 touches
1 conflict
0x3902acf0…1046
0x34b655…2a6f
4 touches
1 conflict
0x4930633b…894e
0x34b655…2a6f
4 touches
1 conflict
0x52a2ba74…f2f6
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity