← previous blocknext block →recent activity

Analyzing

Block #74,635,290

17 transactions · 13 stateful · 2026-05-14 23:32:37 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,635,290  ·  17 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

0x237be61e…e4a6

0xd32edf…ff58

7 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x47c9e028…2bb8

0x065c9d…c394

6 touches
3 conflicts

0xcd510377…571e

0xee8c0e…1242

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x6609dc6a…a0ec

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xb02793…e402

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 0x237be61e9f…7fe4a6

← previous block·next block →recent activity