← previous blocknext block →recent activity

Analyzing

Block #74,304,816

38 transactions · 28 stateful · 2026-05-13 10:45:24 UTC

Parallelism

74/100

Blocked

68%

Avg conflicts / tx

1.63

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,304,816  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xefe9dcd4…6bc2

0xd32edf…ff58

19 touches
45 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

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

45 conflicts on slot 0xefe9dcd44b…736bc2

← previous block·next block →recent activity