← previous blocknext block →recent activity
Analyzing
Block #83,759,239
23 transactions · 20 stateful · 2026-06-26 06:08:37 UTC
Parallelism
74/100
Blocked
55%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,759,239 · 23 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
1w02w13w24w26w37w48w49w514w016w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9db7b4d…2957
0x40c49f…2af0
8 touches
6 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
8 touches
6 conflicts
0x3f4dc602…5a18
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf8a0cebb…b351
0x40c49f…2af0
4 touches
2 conflicts
0x5581d709…ab77
0x2a68ba…90c5
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 0xa9db7b4dd0…562957
Audit this contract →
← previous block·next block →recent activity