← previous blocknext block →recent activity

Analyzing

Block #75,129,544

11 transactions · 8 stateful · 2026-05-17 06:32:56 UTC

Parallelism

73/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x1e72ea81…8d8e

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x26faff5d…6de7

0x065c9d…c394

2 touches
0 conflicts

0x3db35068…c16c

0x065c9d…c394

2 touches
0 conflicts

0x436c57e0…51c3

0x065c9d…c394

2 touches
0 conflicts

0x75be23f4…7fe1

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