← previous blocknext block →recent activity

Analyzing

Block #75,005,440

15 transactions · 11 stateful · 2026-05-16 16:45:00 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,005,440  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0xf33bc3d7…5b27

0xd32edf…ff58

5 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x968bdacb…f461

0x2a68ba…90c5

4 touches
1 conflict

0xc9e4fb9a…8965

0x065c9d…c394

3 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

3 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity