← previous blocknext block →recent activity

Analyzing

Block #74,356,069

30 transactions · 24 stateful · 2026-05-13 16:26:14 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,356,069  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x180e8c27…e601

0xd32edf…ff58

11 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xa22f4eea…7f3b

0x065c9d…c394

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

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 0x180e8c2770…47e601

← previous block·next block →recent activity