← previous blocknext block →recent activity

Analyzing

Block #74,352,863

35 transactions · 26 stateful · 2026-05-13 16:04:52 UTC

Parallelism

71/100

Blocked

65%

Avg conflicts / tx

1.23

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,352,863  ·  35 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x6fc73f2d…289d

0xd32edf…ff58

9 touches
10 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x2b093939…9084

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x1c348b58…836a

0x34b655…2a6f

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity