← previous blocknext block →recent activity

Analyzing

Block #74,439,348

17 transactions · 13 stateful · 2026-05-14 01:40:36 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,439,348  ·  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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xb7288040…e44a

0xd32edf…ff58

5 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x52cf5a2f…9694

0x065c9d…c394

4 touches
1 conflict

0x811895e0…11cc

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x7c1a4d31…ee15

0x065c9d…c394

2 touches
0 conflicts

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity