← previous blocknext block →recent activity

Analyzing

Block #74,510,682

39 transactions · 32 stateful · 2026-05-14 09:36:05 UTC

Parallelism

80/100

Blocked

53%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,510,682  ·  39 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

10 touches
10 conflicts

0x8d0e98f3…7ba0

0x34b655…2a6f

10 touches
10 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xcc07e63b…8688

0xd32edf…ff58

7 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

21 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity