← previous blocknext block →recent activity

Analyzing

Block #74,257,622

11 transactions · 7 stateful · 2026-05-13 05:31:28 UTC

Parallelism

73/100

Blocked

29%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,257,622  ·  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

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0xa091f21b…7f7f

0x065c9d…c394

3 touches
1 conflict

0x2d0d108f…388c

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5148382e…82c3

0x065c9d…c394

2 touches
0 conflicts

0xa5e1a737…b111

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

0x065c9d…c394

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity