← previous blocknext block →recent activity

Analyzing

Block #75,526,343

24 transactions · 17 stateful · 2026-05-19 02:52:47 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,526,343  ·  24 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

0x892daf6e…48d8

0x065c9d…c394

8 touches
6 conflicts

0x0b90d7fb…844e

0xd32edf…ff58

7 touches
6 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0xc5b431b7…5ef8

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb81

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 0x892daf6e5d…6d48d8

← previous block·next block →recent activity