← previous blocknext block →recent activity
Analyzing
Block #90,793,626
17 transactions · 17 stateful · 2026-07-27 14:18:43 UTC
Parallelism
53/100
Blocked
59%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,793,626 · 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
2w03w14w25w36w47w58w29w311w414w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff17d0df…a91f
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
8 touches
6 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0x7b67f6cf…0aab
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
10 conflicts on slot 0xff17d0dff5…47a91f
Audit this contract →
← previous block·next block →recent activity