← previous blocknext block →recent activity
Analyzing
Block #90,292,382
17 transactions · 17 stateful · 2026-07-25 20:03:33 UTC
Parallelism
53/100
Blocked
59%
Avg conflicts / tx
1.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,292,382 · 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
2w03w14w25w36w47w58w611w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x17fa2c17…5797
0x34b655…2a6f
6 touches
3 conflicts
0x57998639…d04d
0x34b655…2a6f
6 touches
3 conflicts
0xc771a8d6…f4b9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
6 touches
3 conflicts
0x8b7af792…9ef0
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity