← previous blocknext block →recent activity
Analyzing
Block #90,789,394
25 transactions · 23 stateful · 2026-07-27 13:57:26 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,789,394 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w110w111w212w315w016w217w118w419w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x7b703e52…41df
0x34b655…2a6f
6 touches
3 conflicts
0x05114fa1…7f23
0x34b655…2a6f
6 touches
3 conflicts
0x0494220d…abf6
0x34b655…2a6f
6 touches
3 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: Perpl
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity