← previous blocknext block →recent activity
Analyzing
Block #87,705,845
23 transactions · 20 stateful · 2026-07-14 13:08:14 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,705,845 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w210w311w415w117w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5a7d1163…96ce
0x40c49f…2af0
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x9eb155db…f714
0x34b655…2a6f
4 touches
1 conflict
0xa9988d79…09ff
0x34b655…2a6f
4 touches
1 conflict
0xad0c7701…1d83
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity