← previous blocknext block →recent activity

Analyzing

Block #75,516,355

26 transactions · 21 stateful · 2026-05-19 01:44:35 UTC

Parallelism

62/100

Blocked

71%

Avg conflicts / tx

1.88

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,516,355  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

16 touches
28 conflicts

0x5086c64a…28ba

0x34b655…2a6f

12 touches
15 conflicts

0xaa7a2fe5…1178

0x34b655…2a6f

8 touches
6 conflicts

0xe6bfc435…b5e9

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0xb1526c23…f2b5

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity