← previous blocknext block →recent activity
Analyzing
Block #90,222,509
16 transactions · 16 stateful · 2026-07-25 14:10:38 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,222,509 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x46db48f8…9bff
0x34b655…2a6f
4 touches
1 conflict
0x59572298…7f94
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
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 0x7aad02c682…feb979
Audit this contract →
← previous block·next block →recent activity