← previous blocknext block →recent activity

Analyzing

Block #74,389,120

9 transactions · 7 stateful · 2026-05-13 20:06:13 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,389,120  ·  9 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

0xa47213d1…3273

0x065c9d…c394

4 touches
1 conflict

0x2129bf27…dccb

0x065c9d…c394

3 touches
1 conflict

0xebe0a822…60eb

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xbb95558d…66a5

0x065c9d…c394

2 touches
0 conflicts

0xc4289497…c65e

0x065c9d…c394

2 touches
0 conflicts

0xcc8cdcd8…1305

0x065c9d…c394

2 touches
0 conflicts

0xf32507a0…bfee

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 0xa47213d13a…6e3273

← previous block·next block →recent activity