← previous blocknext block →recent activity

Analyzing

Block #74,260,136

24 transactions · 18 stateful · 2026-05-13 05:48:08 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,260,136  ·  24 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

0x947f96e3…0f6c

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

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

6 conflicts on slot 0x947f96e37b…3e0f6c

← previous block·next block →recent activity