← previous blocknext block →recent activity

Analyzing

Block #74,763,083

38 transactions · 32 stateful · 2026-05-15 13:45:43 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

1.47

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,763,083  ·  38 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x7d9dfbd9…732d

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x49f69157…4445

0x34b655…2a6f

6 touches
3 conflicts

0x729c91b8…9539

0x188d58…ea8e

4 touches
1 conflict

0xe8adf936…34b0

0x188d58…ea8e

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

36 conflicts on slot 0x7d9dfbd9e5…80732d

← previous block·next block →recent activity