← previous blocknext block →recent activity

Analyzing

Block #74,353,142

30 transactions · 23 stateful · 2026-05-13 16:06:43 UTC

Parallelism

73/100

Blocked

39%

Avg conflicts / tx

0.73

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,353,142  ·  30 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

0x3fb0d538…764c

0xd32edf…ff58

11 touches
15 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

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

15 conflicts on slot 0x3fb0d53864…d9764c

← previous block·next block →recent activity