← previous blocknext block →recent activity

Analyzing

Block #91,190,617

19 transactions · 16 stateful · 2026-07-28 23:36:53 UTC

Parallelism

89/100

Blocked

31%

Avg conflicts / tx

0.26

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,190,617  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0000

0x5f96ae…6b89

4 touches
1 conflict

0x00000000…0002

0x5f96ae…6b89

4 touches
1 conflict

0x00000000…0000

0x7214fb…5853

4 touches
1 conflict

0x00000000…0002

0x7214fb…5853

4 touches
1 conflict

0x00000000…0003

0x7214fb…5853

4 touches
1 conflict

0x9ba58458…a450

0x11ed3b…2c96

4 touches
1 conflict

0x6fe7d366…78ff

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 0x0000000000…00003d

← previous block·next block →recent activity