← previous blocknext block →recent activity
Analyzing
Block #87,758,774
34 transactions · 32 stateful · 2026-07-14 19:02:26 UTC
Parallelism
65/100
Blocked
72%
Avg conflicts / tx
1.97
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,758,774 · 34 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w17w08w19w210w011w012w113w214w315w416w518w120w624w126w227w429w533w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x9001f549…089d
0x34b655…2a6f
10 touches
10 conflicts
0xdc204ea3…f1a3
0x34b655…2a6f
10 touches
10 conflicts
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0xaa643d44…2122
0x34b655…2a6f
8 touches
6 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