← previous blocknext block →recent activity
Analyzing
Block #87,690,040
22 transactions · 21 stateful · 2026-07-14 11:22:18 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,690,040 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w416w517w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
12 touches
15 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
10 touches
10 conflicts
0xed59b1cd…8509
0x34b655…2a6f
10 touches
10 conflicts
0xd034b722…ca3a
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 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity