← previous blocknext block →recent activity
Analyzing
Block #87,738,748
21 transactions · 21 stateful · 2026-07-14 16:48:30 UTC
Parallelism
48/100
Blocked
62%
Avg conflicts / tx
2.19
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,738,748 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w59w610w718w819w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
10 touches
10 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
10 touches
10 conflicts
0x58620f29…db5a
0x34b655…2a6f
10 touches
10 conflicts
0x5c591136…d322
0x34b655…2a6f
10 touches
10 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
10 touches
10 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity