← previous blocknext block →recent activity

Analyzing

Block #75,556,300

39 transactions · 31 stateful · 2026-05-19 06:11:55 UTC

Parallelism

67/100

Blocked

65%

Avg conflicts / tx

1.79

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #75,556,300  ·  39 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0xa46d3e49…3690

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xc1baef71…0689

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x5086c64a…28ba

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity