← previous blocknext block →recent activity

Analyzing

Block #74,607,822

24 transactions · 23 stateful · 2026-05-14 20:29:33 UTC

Parallelism

29/100

Blocked

70%

Avg conflicts / tx

5.67

Longest chain

17 deep

Execution timeline

did this block parallelize well?

view

block #74,607,822  ·  24 txs across 17 waves  ·  depth 17
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

wave w15

wave w16

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

0x536e2740…61ac

0x3bd359…433a

34 touches
136 conflicts

0x00000000…0002

0xa7283d…0ace

34 touches
136 conflicts

0xa472d565…9fe4

0x3bd359…433a

34 touches
136 conflicts

0xeda067d3…97b3

0xa7283d…0ace

32 touches
120 conflicts

0x8fa7a69c…8fd7

0x5ee258…7777

32 touches
120 conflicts

0xeda067d3…97b0

0xa7283d…0ace

32 touches
120 conflicts

0xeda067d3…97b1

0xa7283d…0ace

32 touches
120 conflicts

0xeda067d3…97b2

0xa7283d…0ace

32 touches
120 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: 0x3bd359c1…15433a

136 conflicts on slot 0x536e2740da…e461ac

← previous block·next block →recent activity