← previous blocknext block →recent activity

Analyzing

Block #74,679,696

14 transactions · 11 stateful · 2026-05-15 04:28:53 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,679,696  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0x10814d14…cdda

0x34b655…2a6f

2 touches
0 conflicts

0x1219f4e6…5013

0x34b655…2a6f

2 touches
0 conflicts

0x23c095cc…6318

0x34b655…2a6f

2 touches
0 conflicts

0x3552a26a…ce1f

0x34b655…2a6f

2 touches
0 conflicts

0x38a04dd1…8c24

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity