← previous blocknext block →recent activity

Analyzing

Block #75,139,621

10 transactions · 9 stateful · 2026-05-17 07:40:04 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,139,621  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x84d2dd79…2e57

0x065c9d…c394

4 touches
1 conflict

0x91dad25f…8332

0x065c9d…c394

4 touches
1 conflict

0x2cb2a40d…31c3

0x065c9d…c394

3 touches
1 conflict

0xaa6575f6…529c

0x065c9d…c394

3 touches
1 conflict

0xff31ee36…10bb

0x065c9d…c394

3 touches
1 conflict

0x57567683…566e

0x065c9d…c394

3 touches
1 conflict

0x5ad1cdb7…7dd1

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x84d2dd79af…752e57

← previous block·next block →recent activity