← previous blocknext block →recent activity

Analyzing

Block #74,353,118

21 transactions · 17 stateful · 2026-05-13 16:06:34 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,353,118  ·  21 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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8f443408…cf6c

0xd32edf…ff58

7 touches
6 conflicts

0xba5743c7…21c0

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x729c91b8…9539

0x188d58…ea8e

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity