← previous blocknext block →recent activity

Analyzing

Block #74,224,944

25 transactions · 21 stateful · 2026-05-13 01:54:15 UTC

Parallelism

76/100

Blocked

52%

Avg conflicts / tx

1.04

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,224,944  ·  25 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

0x1feae7df…f1f4

0xd32edf…ff58

11 touches
15 conflicts

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x36e80323…4929

0x699abc…6a3b

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 0x1feae7df14…c8f1f4

← previous block·next block →recent activity