← previous blocknext block →recent activity

Analyzing

Block #75,262,553

24 transactions · 20 stateful · 2026-05-17 21:21:19 UTC

Parallelism

67/100

Blocked

65%

Avg conflicts / tx

1.08

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,262,553  ·  24 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

0xed504e9e…5c12

0xd32edf…ff58

11 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

10 touches
10 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

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: 0xd32edf66…9fff58

15 conflicts on slot 0xed504e9e17…435c12

← previous block·next block →recent activity