← previous blocknext block →recent activity

Analyzing

Block #75,097,987

18 transactions · 8 stateful · 2026-05-17 03:02:18 UTC

Parallelism

83/100

Blocked

25%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,097,987  ·  18 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

0x2c52beae…6a2c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x388f889f…a655

0x34b655…2a6f

5 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x2cf96c0a…538a

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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: 0x34b6552d…112a6f

3 conflicts on slot 0x2c52beae18…856a2c

← previous block·next block →recent activity