← previous blocknext block →recent activity
Analyzing
Block #87,700,169
98 transactions · 64 stateful · 2026-07-14 12:30:02 UTC
Parallelism
83/100
Blocked
70%
Avg conflicts / tx
2.65
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,700,169 · 98 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w18w09w110w219w022w225w027w128w230w331w433w535w636w738w839w941w1042w1167w169w370w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
30 touches
105 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…003d
0xa6afd3…d132
30 touches
105 conflicts
0x006ee1d9…5485
0xa6afd3…d132
28 touches
91 conflicts
0xbcdee322…f454
0xa6afd3…d132
28 touches
91 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
28 touches
91 conflicts
0x5778d110…d2e6
0xc8689a…ee79
28 touches
91 conflicts
0xdb067026…9eb8
0x2b46c0…1669
28 touches
91 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
105 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity