← previous blocknext block →recent activity
Analyzing
Block #90,499,239
21 transactions · 19 stateful · 2026-07-26 13:37:46 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,499,239 · 21 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
2w06w18w29w010w312w114w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2066fe8e…f5d6
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x7150753f…7e32
0x34b655…2a6f
4 touches
1 conflict
0xa8a50028…fed6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity