← previous blocknext block →recent activity
Analyzing
Block #90,209,242
15 transactions · 13 stateful · 2026-07-25 13:03:43 UTC
Parallelism
60/100
Blocked
54%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,209,242 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w38w410w513w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0x0728ec77…146c
0x34b655…2a6f
6 touches
3 conflicts
0xdd8f56bb…a65f
0x34b655…2a6f
6 touches
3 conflicts
0xe8e48b9a…0987
0x34b655…2a6f
6 touches
3 conflicts
0x91aad542…414f
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 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity