← previous blocknext block →recent activity

Analyzing

Block #75,470,924

9 transactions · 7 stateful · 2026-05-18 20:34:33 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,470,924  ·  9 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

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0x0b1bc8f2…ba91

0x065c9d…c394

3 touches
1 conflict

0x0b4ac884…a628

0x065c9d…c394

3 touches
1 conflict

0xa605468c…1bfc

0x1d1325…2305

2 touches
0 conflicts

0xc8525006…2b45

0x1d1325…2305

2 touches
0 conflicts

0x00000000…006f

0x1efe02…37d6

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 0x5f77d60791…b12c84

← previous block·next block →recent activity