← previous blocknext block →recent activity

Analyzing

Block #75,479,161

32 transactions · 22 stateful · 2026-05-18 21:29:29 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,479,161  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x7e3d750f…04fd

0x34b655…2a6f

10 touches
10 conflicts

0xf85c75bc…00b5

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x10abefc9…c9bc

0x1d1325…2305

6 touches
3 conflicts

0x10d80fee…dbda

0x1d1325…2305

6 touches
3 conflicts

0xdb067026…9eb8

0x1d1325…2305

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity