← previous blocknext block →recent activity
Analyzing
Block #87,735,173
32 transactions · 32 stateful · 2026-07-14 16:24:35 UTC
Parallelism
40/100
Blocked
59%
Avg conflicts / tx
3.28
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,735,173 · 32 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w611w712w813w917w1020w1329w1631w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
24 touches
66 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x5b145de0…367c
0xc8689a…ee79
20 touches
45 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
20 touches
45 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
20 touches
45 conflicts
0x58620f29…db5a
0x34b655…2a6f
20 touches
45 conflicts
0x84d74093…7808
0x34b655…2a6f
20 touches
45 conflicts
0x850a8c7a…5d8f
0x34b655…2a6f
14 touches
21 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
66 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity