← previous blocknext block →recent activity

Analyzing

Block #74,352,810

29 transactions · 23 stateful · 2026-05-13 16:04:31 UTC

Parallelism

83/100

Blocked

52%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,352,810  ·  29 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

0x6b01bd04…e7eb

0xd32edf…ff58

7 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0xba5743c7…21c0

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

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 0x6b01bd0416…75e7eb

← previous block·next block →recent activity