← previous blocknext block →recent activity
Analyzing
Block #91,079,053
32 transactions · 30 stateful · 2026-07-28 14:15:36 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,079,053 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w011w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
14 touches
21 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x5891d42e…580b
0x7b9256…1fb2
8 touches
6 conflicts
0x5891d42e…580c
0x7b9256…1fb2
8 touches
6 conflicts
0x5891d42e…580f
0x7b9256…1fb2
8 touches
6 conflicts
0x5e370792…a915
0x7b9256…1fb2
8 touches
6 conflicts
0x5e370792…a916
0x7b9256…1fb2
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity