← previous blocknext block →recent activity

Analyzing

Block #74,344,934

36 transactions · 25 stateful · 2026-05-13 15:12:11 UTC

Parallelism

72/100

Blocked

68%

Avg conflicts / tx

1.58

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,344,934  ·  36 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

18 touches
36 conflicts

0x9f300027…be0b

0xd32edf…ff58

11 touches
15 conflicts

0xeebd31ac…0794

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0xb0e4f69d…34e2

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity