← previous blocknext block →recent activity

Analyzing

Block #74,247,604

39 transactions · 30 stateful · 2026-05-13 04:24:54 UTC

Parallelism

80/100

Blocked

60%

Avg conflicts / tx

1.08

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,247,604  ·  39 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

0x1b8c388e…0382

0xd32edf…ff58

11 touches
15 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

8 touches
6 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 0x1b8c388eae…2a0382

← previous block·next block →recent activity