← previous blocknext block →recent activity
Analyzing
Block #90,066,366
24 transactions · 23 stateful · 2026-07-25 01:01:08 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,066,366 · 24 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
3w04w05w110w213w315w016w117w218w319w421w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x4bc1abab…5874
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0x1741dbc0…73a7
0x34b655…2a6f
8 touches
6 conflicts
0xf93551d2…94e1
0x34b655…2a6f
7 touches
6 conflicts
0xc824469a…6425
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
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity