← previous blocknext block →recent activity

Analyzing

Block #74,915,409

14 transactions · 13 stateful · 2026-05-16 06:42:07 UTC

Parallelism

79/100

Blocked

23%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,915,409  ·  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

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0x1645bc1d…057d

0x065c9d…c394

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x578e7f66…1b56

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x96af6949…d7d2

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity