← previous blocknext block →recent activity

Analyzing

Block #74,650,811

27 transactions · 23 stateful · 2026-05-15 01:15:56 UTC

Parallelism

85/100

Blocked

48%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,650,811  ·  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

0x31448c2e…e73e

0xd32edf…ff58

7 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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 0x31448c2e5e…38e73e

← previous block·next block →recent activity