← previous blocknext block →recent activity
Analyzing
Block #90,698,665
22 transactions · 20 stateful · 2026-07-27 06:20:59 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,698,665 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w08w19w010w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7676b34…7209
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0x67d846dd…358c
0x609679…7777
6 touches
3 conflicts
0x02059d37…b643
0x9f3832…4ae4
6 touches
3 conflicts
0x02059d37…b644
0x9f3832…4ae4
6 touches
3 conflicts
0x6faf6baf…150d
0x9f3832…4ae4
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
6 conflicts on slot 0xf7676b34ed…517209
Audit this contract →
← previous block·next block →recent activity