← previous blocknext block →recent activity

Analyzing

Block #75,103,160

18 transactions · 17 stateful · 2026-05-17 03:36:48 UTC

Parallelism

61/100

Blocked

41%

Avg conflicts / tx

0.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,103,160  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0xb2340eee…cfe0

0xd32edf…ff58

7 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0xc75a1e50…214a

0x065c9d…c394

4 touches
2 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity