← previous blocknext block →recent activity

Analyzing

Block #98,950,496

16 transactions · 16 stateful · 2026-08-25 04:37:32 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,950,496  ·  16 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

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x2a07e64e…fe77

0x754704…b603

4 touches
1 conflict

0x00000000…0008

0x8964d7…10f8

4 touches
1 conflict

0x2d5e16ce…eb10

0x8964d7…10f8

4 touches
1 conflict

0x2d5e16ce…eb11

0x8964d7…10f8

4 touches
1 conflict

0x2d5e16ce…eb14

0x8964d7…10f8

4 touches
1 conflict

0x2d5e16ce…eb15

0x8964d7…10f8

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