← previous blocknext block →recent activity

Analyzing

Block #74,389,273

15 transactions · 14 stateful · 2026-05-13 20:07:15 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,389,273  ·  15 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

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x9fe2ed69…5e2a

0x065c9d…c394

5 touches
3 conflicts

0xac33ff75…077b

0xfa32f9…f3f0

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xffe004da…e2f4

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0001

0xfa32f9…f3f0

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 0x1c38946843…a16b0e

← previous block·next block →recent activity