← previous blocknext block →recent activity
Analyzing
Block #87,920,236
27 transactions · 19 stateful · 2026-07-15 13:02:26 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,920,236 · 27 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
2w03w17w08w113w214w016w119w020w121w022w223w324w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb6aaff6…d579
0x34b655…2a6f
8 touches
6 conflicts
0x5d863b2f…bd28
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe3ab3114…678a
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
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 0xdb6aaff602…46d579
Audit this contract →
← previous block·next block →recent activity