← previous blocknext block →recent activity

Analyzing

Block #74,457,202

39 transactions · 30 stateful · 2026-05-14 03:39:29 UTC

Parallelism

82/100

Blocked

63%

Avg conflicts / tx

1.59

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,457,202  ·  39 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xad28a67c…d3f1

0xd32edf…ff58

13 touches
21 conflicts

0x1c389468…6b0e

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xb8228d38…3953

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: 0xd32edf66…9fff58

21 conflicts on slot 0xad28a67c42…0ed3f1

← previous block·next block →recent activity