← previous blocknext block →recent activity

Analyzing

Block #74,247,629

29 transactions · 24 stateful · 2026-05-13 04:25:04 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,247,629  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc5dae718…051d

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0003

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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

15 conflicts on slot 0xc5dae718d7…fb051d

← previous block·next block →recent activity