← previous blocknext block →recent activity
Analyzing
Block #91,008,779
18 transactions · 17 stateful · 2026-07-28 08:21:53 UTC
Parallelism
61/100
Blocked
35%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,008,779 · 18 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
1w02w13w24w35w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
14 touches
21 conflicts
0x77a99df7…d784
0x851145…3f07
14 touches
21 conflicts
0x1b6c23a0…723b
0x851145…3f07
14 touches
21 conflicts
0x466a76c3…7a61
0x851145…3f07
14 touches
21 conflicts
0x7a12283f…b18a
0x2b46c0…1669
10 touches
10 conflicts
0x915c095e…c1e5
0x2b46c0…1669
10 touches
10 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
10 touches
10 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
10 touches
10 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: 0x851145ea…9f3f07
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity