← previous blocknext block →recent activity

Analyzing

Block #74,319,427

26 transactions · 24 stateful · 2026-05-13 12:22:38 UTC

Parallelism

81/100

Blocked

46%

Avg conflicts / tx

0.96

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,319,427  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x0cb5b886…beee

0x34b655…2a6f

8 touches
6 conflicts

0xc2c1c350…c3b8

0xd32edf…ff58

7 touches
6 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xeeb38aa7…8f00

0x34b655…2a6f

5 touches
3 conflicts

0x3b53436c…2ec3

0x34b655…2a6f

4 touches
1 conflict

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity