← previous blocknext block →recent activity

Analyzing

Block #89,871,869

15 transactions · 15 stateful · 2026-07-24 08:41:22 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,871,869  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x529e53cf…38e4

0xa6afd3…d132

6 touches
3 conflicts

0x989252a1…d812

0xa6afd3…d132

6 touches
3 conflicts

0xa86351b8…2c5a

0x34b655…2a6f

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x4dd19eaa…75bd

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity