← previous blocknext block →recent activity

Analyzing

Block #74,434,366

29 transactions · 27 stateful · 2026-05-14 01:07:29 UTC

Parallelism

76/100

Blocked

48%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,434,366  ·  29 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

0xadac4a86…c2bc

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xe23f9887…6cc8

0xd32edf…ff58

9 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xb8228d38…3953

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

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

15 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity