← previous blocknext block →recent activity
Analyzing
Block #86,136,279
26 transactions · 23 stateful · 2026-07-07 06:14:17 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,136,279 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w49w019w120w122w023w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e28e55c…d05c
0x754704…b603
6 touches
3 conflicts
0x00000000…0001
0x659bd0…a9da
6 touches
3 conflicts
0x00000000…0000
0x659bd0…a9da
6 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
6 touches
3 conflicts
0x9d29a714…51ee
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity