← previous blocknext block →recent activity

Analyzing

Block #75,687,405

13 transactions · 10 stateful · 2026-05-19 20:47:11 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,687,405  ·  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

0x4535d4aa…7422

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x9b1a47c3…69f8

0xde22b2…7777

4 touches
1 conflict

0xdfa159d0…1576

0x065c9d…c394

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: 0xd32edf66…9fff58

6 conflicts on slot 0x4535d4aa8a…dc7422

← previous block·next block →recent activity