← previous blocknext block →recent activity
Analyzing
Block #92,070,217
15 transactions · 13 stateful · 2026-08-01 01:24:05 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,070,217 · 15 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
1w02w13w04w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c8898de…8758
0x34b655…2a6f
8 touches
6 conflicts
0xc87e767e…4bba
0x34b655…2a6f
6 touches
3 conflicts
0xbffde283…3385
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x20fb35c7…09c2
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
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: Perpl
6 conflicts on slot 0x6c8898de19…1f8758
Audit this contract →
← previous block·next block →recent activity