← previous blocknext block →recent activity
Analyzing
Block #87,786,867
26 transactions · 24 stateful · 2026-07-14 22:10:24 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,786,867 · 26 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
1w02w13w28w09w110w011w115w217w318w122w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8703b357…cb0c
0x34b655…2a6f
4 touches
1 conflict
0xad15ca0d…a3d5
0x34b655…2a6f
4 touches
1 conflict
0xd972ea45…48b5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity