← previous blocknext block →recent activity
Analyzing
Block #90,800,643
26 transactions · 21 stateful · 2026-07-27 14:54:02 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,800,643 · 26 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
4w05w18w09w111w213w215w316w317w420w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69c491e3…98d9
0x34b655…2a6f
6 touches
3 conflicts
0xfe6f15d9…6683
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x28c714d9…9438
0xa6afd3…d132
6 touches
3 conflicts
0xb566cc65…214d
0xa6afd3…d132
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x69c491e302…ce98d9
Audit this contract →
← previous block·next block →recent activity