← previous blocknext block →recent activity
Analyzing
Block #86,249,226
18 transactions · 14 stateful · 2026-07-07 18:48:28 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,249,226 · 18 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
2w03w14w05w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xe7069f55…cdd9
0x40c49f…2af0
6 touches
3 conflicts
0x68ebc592…026d
0x40c49f…2af0
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x7754e0f5…d02e
0x34b655…2a6f
4 touches
1 conflict
0xca411fd0…9734
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity