← previous blocknext block →recent activity
Analyzing
Block #90,232,020
18 transactions · 14 stateful · 2026-07-25 14:58:35 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,232,020 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w110w011w112w213w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e0a3c1a…f9fb
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf394e6ad…f568
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x28392d8a…0354
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
6 conflicts on slot 0x0e0a3c1a06…e6f9fb
Audit this contract →
← previous block·next block →recent activity