← previous blocknext block →recent activity

Analyzing

Block #75,740,779

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

Parallelism

62/100

Blocked

36%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xdfa159d0…1576

0x065c9d…c394

6 touches
3 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x456dea64…f66d

0x065c9d…c394

4 touches
1 conflict

0x45928e27…fe08

0x065c9d…c394

4 touches
1 conflict

0x5d6f438a…a3e4

0x065c9d…c394

4 touches
1 conflict

0x4ea9ba3f…57fc

0x065c9d…c394

3 touches
1 conflict

0xdc61acbf…2ead

0x065c9d…c394

3 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity