← previous blocknext block →recent activity

Analyzing

Block #74,377,016

14 transactions · 10 stateful · 2026-05-13 18:45:37 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,377,016  ·  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

0x7e35d721…8b5e

0x065c9d…c394

4 touches
1 conflict

0xa791b18e…7a7b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0xc05d8296…5d8d

0x065c9d…c394

3 touches
1 conflict

0xc42a4a2b…32bf

0x065c9d…c394

3 touches
1 conflict

0x52a12cd9…8f6d

0xd32edf…ff58

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

1 conflict on slot 0x7e35d72198…e98b5e

← previous block·next block →recent activity