← previous blocknext block →recent activity

Analyzing

Block #74,767,994

17 transactions · 13 stateful · 2026-05-15 14:18:38 UTC

Parallelism

65/100

Blocked

54%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,767,994  ·  17 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

0xaac0476a…224a

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x07183925…5c95

0x34b655…2a6f

4 touches
1 conflict

0xa11bd7ea…20b4

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

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

15 conflicts on slot 0xaac0476a26…86224a

← previous block·next block →recent activity