← previous blocknext block →recent activity

Analyzing

Block #74,773,230

24 transactions · 11 stateful · 2026-05-15 14:53:40 UTC

Parallelism

92/100

Blocked

36%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,773,230  ·  24 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1a6bf05b…05d7

0x065c9d…c394

3 touches
1 conflict

0x8f478f26…9d56

0x000000…012a

2 touches
0 conflicts

0x9cafc3b6…ee8c

0x000000…012a

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0xc3006de0…9726

0x188d58…ea8e

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: 0x754704bc…afb603

1 conflict on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity