← previous blocknext block →recent activity

Analyzing

Block #74,353,026

35 transactions · 21 stateful · 2026-05-13 16:05:57 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

1.11

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,353,026  ·  35 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xa62af9a2…56c1

0xd32edf…ff58

15 touches
28 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

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

28 conflicts on slot 0xa62af9a2ed…1156c1

← previous block·next block →recent activity