← previous blocknext block →recent activity

Analyzing

Block #75,740,880

13 transactions · 11 stateful · 2026-05-20 02:42:57 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,740,880  ·  13 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

0x06e377e6…77be

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d077ae2…f4d3

0x065c9d…c394

2 touches
0 conflicts

0x7d3cd397…102d

0x065c9d…c394

2 touches
0 conflicts

0x8a37a5a3…b8e6

0x065c9d…c394

2 touches
0 conflicts

0xa603b1cd…ea04

0x065c9d…c394

2 touches
0 conflicts

0xdfa159d0…1576

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 0x06e377e6df…ee77be

← previous block·next block →recent activity