← previous blocknext block →recent activity
Analyzing
Block #90,617,163
18 transactions · 18 stateful · 2026-07-26 23:30:58 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,617,163 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w29w310w411w213w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b1ce1dd…dc2f
0x34b655…2a6f
6 touches
3 conflicts
0xac33ff75…077b
0xfa32f9…f3f0
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
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
3 conflicts on slot 0x3b1ce1dd02…5adc2f
Audit this contract →
← previous block·next block →recent activity