← previous blocknext block →recent activity

Analyzing

Block #75,479,606

10 transactions · 7 stateful · 2026-05-18 21:32:34 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,479,606  ·  10 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

0xa6afd3…d132

4 touches
1 conflict

0xf85c75bc…00b5

0xa6afd3…d132

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x5bd8ffe7…37fb

0x065c9d…c394

2 touches
0 conflicts

0x892daf6e…48d8

0x065c9d…c394

2 touches
0 conflicts

0x06e40499…165e

0x1d1325…2305

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: 0xa6afd386…b0d132

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity