← previous blocknext block →recent activity

Analyzing

Block #90,604,003

20 transactions · 17 stateful · 2026-07-26 22:24:45 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,604,003  ·  20 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

0xae78b6bc…5853

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xa5811d93…8c73

0x34b655…2a6f

4 touches
1 conflict

0xa6b89ebb…a66e

0x34b655…2a6f

4 touches
1 conflict

0xb5cddf91…0abf

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: 0x40c49f17…d22af0

3 conflicts on slot 0xae78b6bc21…575853

← previous block·next block →recent activity