← previous blocknext block →recent activity

Analyzing

Block #74,745,076

34 transactions · 29 stateful · 2026-05-15 11:45:03 UTC

Parallelism

74/100

Blocked

52%

Avg conflicts / tx

1.09

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,745,076  ·  34 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xb300cc20…742e

0xd32edf…ff58

11 touches
15 conflicts

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x3e49348b…9445

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

8 touches
6 conflicts

0x1da7723c…80a8

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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 0xb300cc20a8…2c742e

← previous block·next block →recent activity