← previous blocknext block →recent activity

Analyzing

Block #75,552,872

29 transactions · 25 stateful · 2026-05-19 05:49:10 UTC

Parallelism

79/100

Blocked

60%

Avg conflicts / tx

1.28

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,552,872  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x49667044…5237

0xd32edf…ff58

11 touches
15 conflicts

0x5086c64a…28ba

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x8725f80c…ff6b

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x9e719c7a…df63

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

15 conflicts on slot 0x49667044db…ec5237

← previous block·next block →recent activity