← previous blocknext block →recent activity

Analyzing

Block #74,041,788

25 transactions · 23 stateful · 2026-05-12 05:35:42 UTC

Parallelism

60/100

Blocked

65%

Avg conflicts / tx

1.76

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,041,788  ·  25 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

0x0f9b918b…212d

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

8 touches
6 conflicts

0x621c802c…4e31

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

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