← previous blocknext block →recent activity

Analyzing

Block #75,098,166

29 transactions · 17 stateful · 2026-05-17 03:03:30 UTC

Parallelism

79/100

Blocked

71%

Avg conflicts / tx

0.97

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,098,166  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity