← previous blocknext block →recent activity
Analyzing
Block #90,791,901
38 transactions · 35 stateful · 2026-07-27 14:10:02 UTC
Parallelism
66/100
Blocked
71%
Avg conflicts / tx
2.13
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #90,791,901 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w210w011w113w214w315w016w117w218w319w420w521w622w724w225w826w928w1030w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x110a671c…e284
0x34b655…2a6f
8 touches
6 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0x4528594e…919a
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity