← previous blocknext block →recent activity

Analyzing

Block #74,920,455

30 transactions · 21 stateful · 2026-05-16 07:15:49 UTC

Parallelism

83/100

Blocked

52%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,920,455  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x35e5f761…0ef6

0xd32edf…ff58

7 touches
6 conflicts

0x93af5ad2…45f1

0x34b655…2a6f

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0x7e5ef403…70a3

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity