← previous blocknext block →recent activity

Analyzing

Block #74,351,642

11 transactions · 10 stateful · 2026-05-13 15:56:44 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,351,642  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x8c220c19…eb3d

0xd32edf…ff58

3 touches
1 conflict

0x3ebf9c2b…5d4b

0x065c9d…c394

2 touches
0 conflicts

0xb6fc02fd…7ca4

0x065c9d…c394

2 touches
0 conflicts

0xe133d834…603b

0x065c9d…c394

2 touches
0 conflicts

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

1 conflict on slot 0x47b807a243…c53307

← previous block·next block →recent activity