← previous blocknext block →recent activity
Analyzing
Block #87,708,732
59 transactions · 38 stateful · 2026-07-14 13:27:32 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.46
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,708,732 · 59 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w111w213w314w415w017w127w128w029w130w231w332w433w534w635w736w837w940w741w844w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
10 touches
10 conflicts
0x767799cd…f423
0xc8689a…ee79
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc03846bb…73b3
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity