← previous blocknext block →recent activity

Analyzing

Block #74,918,629

11 transactions · 7 stateful · 2026-05-16 07:03:36 UTC

Parallelism

73/100

Blocked

29%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,918,629  ·  11 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

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x3ff122a3…95ff

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x062e9ebd…0a0a

0x34b655…2a6f

2 touches
0 conflicts

0x0a991adc…342a

0x34b655…2a6f

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x336241b2…c1db

0x34b655…2a6f

2 touches
0 conflicts

0x3582b315…0ce0

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: 0x065c9d28…a9c394

1 conflict on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity