← previous blocknext block →recent activity

Analyzing

Block #74,351,529

32 transactions · 24 stateful · 2026-05-13 15:55:59 UTC

Parallelism

72/100

Blocked

58%

Avg conflicts / tx

1.38

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,351,529  ·  32 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

0xadde469c…4e21

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x4364afe0…4ec5

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c0

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

36 conflicts on slot 0xadde469c6e…c04e21

← previous block·next block →recent activity