← previous blocknext block →recent activity
Analyzing
Block #90,975,825
9 transactions · 7 stateful · 2026-07-28 05:35:23 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,975,825 · 9 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xf2b36ab5…39d8
0x34b655…2a6f
4 touches
1 conflict
0x14a521c9…ef95
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1ab4c88c…49f2
0x34b655…2a6f
2 touches
0 conflicts
0x1ab4c88c…49f3
0x34b655…2a6f
2 touches
0 conflicts
0x1f396cee…862f
0x34b655…2a6f
2 touches
0 conflicts
0x26909e0e…8f1f
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity