← previous blocknext block →recent activity

Analyzing

Block #74,377,337

20 transactions · 15 stateful · 2026-05-13 18:47:46 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,377,337  ·  20 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xb9b6bf78…1a81

0xd32edf…ff58

5 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: 0x34b6552d…112a6f

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity