← previous blocknext block →recent activity

Analyzing

Block #75,301,555

30 transactions · 21 stateful · 2026-05-18 01:42:29 UTC

Parallelism

73/100

Blocked

52%

Avg conflicts / tx

0.97

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,301,555  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xeebd31ac…0794

0x34b655…2a6f

8 touches
6 conflicts

0x9394e22c…3da3

0x34b655…2a6f

8 touches
6 conflicts

0x58e06bab…34cf

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x737acb78…fce8

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: Perpl

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity