← previous blocknext block →recent activity
Analyzing
Block #90,889,419
13 transactions · 13 stateful · 2026-07-27 22:20:44 UTC
Parallelism
54/100
Blocked
62%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,889,419 · 13 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
1w02w13w24w38w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x002be092…c311
0x34b655…2a6f
6 touches
3 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
6 touches
3 conflicts
0x8a1db511…3ac9
0x34b655…2a6f
6 touches
3 conflicts
0xadc92aaf…3077
0x34b655…2a6f
6 touches
3 conflicts
0x286ff32c…2782
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity