← previous blocknext block →recent activity
Analyzing
Block #90,945,266
10 transactions · 10 stateful · 2026-07-28 03:01:40 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,945,266 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b8368aa…9d5d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74137b07…5880
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0x29f26b03…63b1
0x34b655…2a6f
2 touches
0 conflicts
0x2dd83168…8144
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7b8368aacf…cf9d5d
Audit this contract →
← previous block·next block →recent activity