← previous blocknext block →recent activity

Analyzing

Block #74,352,540

8 transactions · 7 stateful · 2026-05-13 16:02:43 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,352,540  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x256fb14c…b929

0x065c9d…c394

4 touches
1 conflict

0xfb083229…0138

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9dd6bd1b…5cbb

0x065c9d…c394

3 touches
1 conflict

0x3f8b141b…2af3

0x065c9d…c394

3 touches
1 conflict

0x11e56fb6…72bb

0xd32edf…ff58

3 touches
1 conflict

0xfe2bac2b…2cec

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

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity