← previous blocknext block →recent activity

Analyzing

Block #74,353,720

34 transactions · 23 stateful · 2026-05-13 16:10:34 UTC

Parallelism

76/100

Blocked

52%

Avg conflicts / tx

1.03

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,353,720  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6a767ee6…dcfd

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x47b807a2…3307

0x065c9d…c394

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x78694995…f668

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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

15 conflicts on slot 0x6a767ee61f…d7dcfd

← previous block·next block →recent activity