← previous blocknext block →recent activity

Analyzing

Block #90,948,297

12 transactions · 12 stateful · 2026-07-28 03:16:55 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,948,297  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xf219f7cf…7379

0xa6afd3…d132

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x7e1faa73…bfbf

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbbeac3b7…c14b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xed59b1cd…8509

0x34b655…2a6f

4 touches
1 conflict

0xef6f66f4…beea

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

1 conflict on slot 0xf219f7cff4…0f7379

← previous block·next block →recent activity