← previous blocknext block →recent activity
Analyzing
Block #87,730,381
25 transactions · 20 stateful · 2026-07-14 15:52:31 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.8
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,730,381 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w110w212w313w414w515w616w718w820w921w1024w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xc4de6652…13f4
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
6 touches
3 conflicts
0x5c3cb0f1…a9fa
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x67f85008…febc
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity