← previous blocknext block →recent activity
Analyzing
Block #87,738,675
26 transactions · 20 stateful · 2026-07-14 16:48:00 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,738,675 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w010w111w012w113w216w117w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x1a1df941…41d5
0x34b655…2a6f
4 touches
1 conflict
0x28e2214c…9da7
0x34b655…2a6f
4 touches
1 conflict
0x50718952…7c75
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity