← previous blocknext block →recent activity

Analyzing

Block #74,400,573

14 transactions · 7 stateful · 2026-05-13 21:22:29 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,400,573  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfa9c3161…f238

0x065c9d…c394

3 touches
1 conflict

0x86a5cfbc…194a

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x9dc46756…01e2

0x065c9d…c394

2 touches
0 conflicts

0x9df6d06b…85e7

0x065c9d…c394

2 touches
0 conflicts

0xcec8aa8d…ea1c

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity