← previous blocknext block →recent activity

Analyzing

Block #74,240,921

15 transactions · 11 stateful · 2026-05-13 03:40:28 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,240,921  ·  15 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

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x14a5c59c…1efb

0xd32edf…ff58

5 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x659eb85f…85b1

0x065c9d…c394

3 touches
1 conflict

0x86bcc243…a563

0x065c9d…c394

3 touches
1 conflict

0xfb083229…0138

0x2a68ba…90c5

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

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

3 conflicts on slot 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity