← previous blocknext block →recent activity
Analyzing
Block #90,795,750
20 transactions · 18 stateful · 2026-07-27 14:29:24 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,795,750 · 20 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
1w04w06w17w010w111w112w213w014w215w317w018w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e0065ad…e39b
0x34b655…2a6f
8 touches
6 conflicts
0x9e599b87…c270
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7632
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 0x3e0065ad02…f8e39b
Audit this contract →
← previous block·next block →recent activity