← previous blocknext block →recent activity

Analyzing

Block #74,643,496

10 transactions · 9 stateful · 2026-05-15 00:27:19 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,643,496  ·  10 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

0xae1f0667…e670

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x62f7c0c0…5b6f

0x065c9d…c394

3 touches
1 conflict

0x9c5ecb3f…639c

0x065c9d…c394

3 touches
1 conflict

0x427a3524…641f

0x065c9d…c394

3 touches
1 conflict

0x53d1c14b…d4b8

0x065c9d…c394

3 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

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: 0x065c9d28…a9c394

1 conflict on slot 0xae1f066717…8ee670

← previous block·next block →recent activity