← previous blocknext block →recent activity

Analyzing

Block #75,262,618

24 transactions · 18 stateful · 2026-05-17 21:21:45 UTC

Parallelism

79/100

Blocked

67%

Avg conflicts / tx

1.17

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,262,618  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xbc1589bc…01c1

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x37202e35…3f71

0x34b655…2a6f

6 touches
3 conflicts

0x55192654…91fe

0x34b655…2a6f

6 touches
3 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity