← previous blocknext block →recent activity

Analyzing

Block #74,284,124

13 transactions · 9 stateful · 2026-05-13 08:27:40 UTC

Parallelism

85/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,284,124  ·  13 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

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x2bd94d82…345e

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x199aa59e…b7fb

0x065c9d…c394

2 touches
0 conflicts

0x31586d48…b45b

0x065c9d…c394

2 touches
0 conflicts

0x88b4001e…17fa

0x065c9d…c394

2 touches
0 conflicts

0xb9aafe7e…2c4e

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 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity