← previous blocknext block →recent activity

Analyzing

Block #74,765,503

30 transactions · 18 stateful · 2026-05-15 14:01:53 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,765,503  ·  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

0x6b1461b6…349f

0xd32edf…ff58

7 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xebc35f88…4b57

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0x6b1461b6fd…cc349f

← previous block·next block →recent activity