← previous blocknext block →recent activity

Analyzing

Block #74,420,641

21 transactions · 15 stateful · 2026-05-13 23:35:58 UTC

Parallelism

86/100

Blocked

47%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,420,641  ·  21 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

0x8357a26a…acf1

0x4fccc9…3d5c

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xab467085…1dde

0x4fccc9…3d5c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7d641894…6b1c

0x4fccc9…3d5c

4 touches
1 conflict

0x37204812…f180

0x4fccc9…3d5c

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: 0x4fccc95f…fa3d5c

3 conflicts on slot 0x8357a26af8…ffacf1

← previous block·next block →recent activity