← previous blocknext block →recent activity

Analyzing

Block #74,920,529

22 transactions · 16 stateful · 2026-05-16 07:16:19 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,920,529  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

6 touches
3 conflicts

0x37674bd8…8f35

0x34b655…2a6f

5 touches
3 conflicts

0x15ce6eb8…6ba1

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x2ce2d49e…d18a

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity