← previous blocknext block →recent activity
Analyzing
Block #90,895,584
17 transactions · 15 stateful · 2026-07-27 22:51:45 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,895,584 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w210w311w412w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9fbc27d…8b3f
0x34b655…2a6f
8 touches
6 conflicts
0x7634a3f4…7f24
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x31152b1f…e76a
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
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
6 conflicts on slot 0xc9fbc27d3b…a18b3f
Audit this contract →
← previous block·next block →recent activity