← previous blocknext block →recent activity

Analyzing

Block #74,356,096

14 transactions · 10 stateful · 2026-05-13 16:26:25 UTC

Parallelism

86/100

Blocked

10%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,356,096  ·  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

0xa7f48c6c…e4cc

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xfb51d0ec…03b7

0xd32edf…ff58

3 touches
1 conflict

0x999eba07…b27e

0x065c9d…c394

2 touches
0 conflicts

0xb692909f…3de2

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0xa7f48c6cb8…3de4cc

← previous block·next block →recent activity