← previous blocknext block →recent activity
Analyzing
Block #87,051,806
19 transactions · 16 stateful · 2026-07-11 12:13:45 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,051,806 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w110w014w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x028f6095…b860
0x34b655…2a6f
6 touches
3 conflicts
0x7103aaf4…ddc5
0x34b655…2a6f
6 touches
3 conflicts
0xa9641aa6…0c3b
0x34b655…2a6f
6 touches
3 conflicts
0x9b373f14…2b2f
0x34b655…2a6f
5 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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity