← previous blocknext block →recent activity

Analyzing

Block #74,298,611

14 transactions · 14 stateful · 2026-05-13 10:04:09 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

1.07

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,298,611  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb9d2cf20…a668

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x3817764d…242b

0x34b655…2a6f

6 touches
3 conflicts

0xad63585b…768d

0x34b655…2a6f

6 touches
3 conflicts

0x1f86dfe6…88e1

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

6 conflicts on slot 0xb9d2cf2005…28a668

← previous block·next block →recent activity