← previous blocknext block →recent activity

Analyzing

Block #75,106,129

18 transactions · 12 stateful · 2026-05-17 03:56:39 UTC

Parallelism

83/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,106,129  ·  18 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

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x02855420…3ea3

0xd32edf…ff58

3 touches
1 conflict

0x17b0eb48…2273

0x065c9d…c394

2 touches
0 conflicts

0x3712b0ac…796c

0x065c9d…c394

2 touches
0 conflicts

0x59fd8b5a…590f

0x065c9d…c394

2 touches
0 conflicts

0x62e241f5…827c

0x065c9d…c394

2 touches
0 conflicts

0x8503fcd8…2697

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 0x348fda08cf…fc7e96

← previous block·next block →recent activity