← previous blocknext block →recent activity
Analyzing
Block #90,866,496
12 transactions · 12 stateful · 2026-07-27 20:25:26 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,866,496 · 12 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
3w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0xd7badc5e…8c2b
0xa6afd3…d132
4 touches
1 conflict
0x4b0212cd…8326
0xa6afd3…d132
3 touches
1 conflict
0x2f0fe1df…da8a
0x34b655…2a6f
2 touches
0 conflicts
0x40bc5adc…eda6
0x34b655…2a6f
2 touches
0 conflicts
0x502b3ee1…7f7b
0x34b655…2a6f
2 touches
0 conflicts
0x502b3ee1…7f7c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity