← previous blocknext block →recent activity

Analyzing

Block #74,763,927

38 transactions · 26 stateful · 2026-05-15 13:51:19 UTC

Parallelism

87/100

Blocked

42%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,763,927  ·  38 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

0x1a524ff5…6751

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

8 touches
6 conflicts

0x9f189645…0acf

0xee8c0e…1242

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

10 conflicts on slot 0x1a524ff5f5…746751

← previous block·next block →recent activity