← previous blocknext block →recent activity

Analyzing

Block #75,124,444

7 transactions · 6 stateful · 2026-05-17 05:58:55 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,124,444  ·  7 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

0xcb6ab2ed…b411

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x50588e95…e576

0x065c9d…c394

3 touches
1 conflict

0x67a32a88…3e9e

0x065c9d…c394

2 touches
0 conflicts

0x9f078360…68c1

0x065c9d…c394

2 touches
0 conflicts

0xa4960c8e…7cd5

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

2 touches
0 conflicts

0xdbd755f8…9027

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 0xcb6ab2ed14…07b411

← previous block·next block →recent activity