← previous blocknext block →recent activity
Analyzing
Block #87,584,166
28 transactions · 18 stateful · 2026-07-13 23:34:36 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,584,166 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w09w110w211w313w015w124w025w126w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0d336deb…3fee
0x34b655…2a6f
6 touches
3 conflicts
0x2fcd4130…b4a5
0xc8689a…ee79
6 touches
3 conflicts
0x33649c4f…b327
0x34b655…2a6f
6 touches
3 conflicts
0x3f24a374…6bc3
0x34b655…2a6f
6 touches
3 conflicts
0x57bb625a…286d
0x34b655…2a6f
6 touches
3 conflicts
0x61043b15…aca5
0x34b655…2a6f
6 touches
3 conflicts
0x64dfceb0…c5d7
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity