← previous blocknext block →recent activity

Analyzing

Block #75,513,177

16 transactions · 14 stateful · 2026-05-19 01:22:52 UTC

Parallelism

63/100

Blocked

57%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,513,177  ·  16 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

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0x019883…2a9a

8 touches
6 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

8 touches
6 conflicts

0x00000000…0000

0x019883…2a9a

8 touches
6 conflicts

0xa10c86f8…4b74

0x3bd359…433a

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

8 touches
6 conflicts

0xd98b3c10…67b8

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

10 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity