← previous blocknext block →recent activity
Analyzing
Block #90,890,416
14 transactions · 14 stateful · 2026-07-27 22:25:45 UTC
Parallelism
64/100
Blocked
29%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,890,416 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w07w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
6 touches
3 conflicts
0x34cfae93…89fb
0x34b655…2a6f
6 touches
3 conflicts
0x424d48b2…e6ae
0x34b655…2a6f
4 touches
1 conflict
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x544474d6…71b4
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 0x9ba6ae4a28…c990cb
Audit this contract →
← previous block·next block →recent activity