← previous blocknext block →recent activity
Analyzing
Block #87,759,832
20 transactions · 19 stateful · 2026-07-14 19:09:31 UTC
Parallelism
60/100
Blocked
42%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,759,832 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x323fde37…d7bc
0x34b655…2a6f
10 touches
10 conflicts
0xd42fdceb…d86a
0x34b655…2a6f
8 touches
6 conflicts
0x33da0dfa…bac6
0x34b655…2a6f
8 touches
6 conflicts
0x5b297152…4446
0x34b655…2a6f
8 touches
6 conflicts
0x323fde37…d7bb
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity