← previous blocknext block →recent activity
Analyzing
Block #90,824,088
15 transactions · 11 stateful · 2026-07-27 16:52:03 UTC
Parallelism
87/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,824,088 · 15 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
3w07w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x10efb0c1…2ddc
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x19cfd958…9c8c
0x34b655…2a6f
2 touches
0 conflicts
0x2097c2f1…f5c3
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x0fffa5c054…49a3a9
Audit this contract →
← previous block·next block →recent activity