← previous blocknext block →recent activity
Analyzing
Block #87,702,932
48 transactions · 38 stateful · 2026-07-14 12:48:39 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
2.06
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,702,932 · 48 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w19w011w112w218w019w120w221w322w423w524w625w726w827w928w1029w1132w1242w145w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
14 touches
21 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
12 touches
15 conflicts
0xad276b7b…ff3f
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity