← previous blocknext block →recent activity
Analyzing
Block #90,875,942
25 transactions · 23 stateful · 2026-07-27 21:12:57 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #90,875,942 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w18w29w310w414w517w621w623w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x80656e3b…9240
0x34b655…2a6f
14 touches
21 conflicts
0x5146ef12…80c6
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x8218911e…3bed
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x588380ee…0a5c
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity