← previous blocknext block →recent activity
Analyzing
Block #91,250,560
38 transactions · 32 stateful · 2026-07-29 04:38:28 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,250,560 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w315w016w117w219w320w421w522w630w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x890a1db9…1712
0xa6afd3…d132
12 touches
15 conflicts
0x2491d756…b71c
0xa6afd3…d132
10 touches
10 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
10 touches
10 conflicts
0xdb067026…9eb8
0x2b46c0…1669
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
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