← previous blocknext block →recent activity
Analyzing
Block #91,394,495
85 transactions · 77 stateful · 2026-07-29 16:43:34 UTC
Parallelism
75/100
Blocked
83%
Avg conflicts / tx
4.56
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #91,394,495 · 85 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w29w311w212w416w419w729w830w931w1033w1234w1335w1462w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
30 touches
105 conflicts
0x7cad3379…e9f7
0xd32edf…ff58
29 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
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: 0x48cba278…e2b48b
105 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity