← previous blocknext block →recent activity
Analyzing
Block #91,763,706
22 transactions · 22 stateful · 2026-07-30 23:42:12 UTC
Parallelism
55/100
Blocked
59%
Avg conflicts / tx
2.23
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,763,706 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w312w413w514w615w716w817w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x74f95963…01a2
0x34b655…2a6f
10 touches
10 conflicts
0xe2e52e46…0894
0x34b655…2a6f
8 touches
6 conflicts
0x0a2300ab…81c7
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
0x5c16527f…628c
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity