← previous blocknext block →recent activity

Analyzing

Block #75,129,547

8 transactions · 7 stateful · 2026-05-17 06:32:57 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,129,547  ·  8 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b934a05…024a

0x065c9d…c394

4 touches
1 conflict

0xa1b13a4e…3928

0x065c9d…c394

3 touches
1 conflict

0x68d0f90a…485f

0x065c9d…c394

3 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x710aa0b3…0999

0x065c9d…c394

2 touches
0 conflicts

0x73e22411…68a0

0x065c9d…c394

2 touches
0 conflicts

0x904936bc…c27e

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 0x0000000000…00003d

← previous block·next block →recent activity