← previous blocknext block →recent activity

Analyzing

Block #75,141,172

11 transactions · 11 stateful · 2026-05-17 07:50:28 UTC

Parallelism

36/100

Blocked

55%

Avg conflicts / tx

1.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,141,172  ·  11 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

14 touches
21 conflicts

0x3e49348b…9445

0x34b655…2a6f

10 touches
10 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

8 touches
6 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x37d49489…9309

0x34b655…2a6f

6 touches
3 conflicts

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0x7ca7baa7…d46d

0x34b655…2a6f

6 touches
3 conflicts

0xac8e97a0…8426

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity