← previous blocknext block →recent activity
Analyzing
Block #90,617,092
23 transactions · 19 stateful · 2026-07-26 23:30:37 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,617,092 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w112w113w214w016w318w119w421w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02213185…bc8d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xb37dfb6b…268f
0x34b655…2a6f
6 touches
3 conflicts
0xc25a3808…72a5
0x34b655…2a6f
6 touches
3 conflicts
0xc7b1189e…d092
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
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 0x0221318531…bebc8d
Audit this contract →
← previous block·next block →recent activity