← previous blocknext block →recent activity
Analyzing
Block #90,697,362
22 transactions · 21 stateful · 2026-07-27 06:14:26 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,697,362 · 22 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
4w05w16w07w18w09w112w213w314w419w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x1a4fb69e…7136
0xa6afd3…d132
8 touches
6 conflicts
0x538f77c2…a9e7
0xa6afd3…d132
8 touches
6 conflicts
0x53d6f1c9…16c4
0x34b655…2a6f
6 touches
3 conflicts
0x91803cbc…2f15
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x408d0052…bda6
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: Kuru Exchange: Market-WETH/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity