← previous blocknext block →recent activity

Analyzing

Block #74,400,051

8 transactions · 8 stateful · 2026-05-13 21:19:01 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,400,051  ·  8 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

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa5a2a48e…17a3

0x065c9d…c394

3 touches
1 conflict

0x298bcc29…3960

0x065c9d…c394

2 touches
0 conflicts

0x5a6b1573…beb7

0x065c9d…c394

2 touches
0 conflicts

0x67d76404…6223

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity