← previous blocknext block →recent activity
Analyzing
Block #90,558,632
16 transactions · 16 stateful · 2026-07-26 18:36:31 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,558,632 · 16 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
4w05w16w27w39w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67f87cdf…e5b6
0x34b655…2a6f
8 touches
6 conflicts
0xf454cca7…095a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x536f894b…2597
0x34b655…2a6f
6 touches
3 conflicts
0x006c3b86…59a9
0x34b655…2a6f
6 touches
3 conflicts
0x680fdd59…e84d
0x34b655…2a6f
6 touches
3 conflicts
0x6f58168d…ea24
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
6 conflicts on slot 0x67f87cdf50…cde5b6
Audit this contract →
← previous block·next block →recent activity