← previous blocknext block →recent activity

Analyzing

Block #74,454,720

27 transactions · 20 stateful · 2026-05-14 03:22:55 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1.37

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,454,720  ·  27 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

0x3f1815a3…44f1

0xd32edf…ff58

15 touches
28 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x6aa624fd…a84e

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 0x3f1815a3ee…f544f1

← previous block·next block →recent activity