← previous blocknext block →recent activity

Analyzing

Block #74,359,802

27 transactions · 17 stateful · 2026-05-13 16:51:03 UTC

Parallelism

85/100

Blocked

47%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,359,802  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x01afc96f…8a86

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

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

6 conflicts on slot 0x01afc96ff8…478a86

← previous block·next block →recent activity