← previous blocknext block →recent activity

Analyzing

Block #73,968,716

9 transactions · 6 stateful · 2026-05-11 21:26:59 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,968,716  ·  9 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

0x192b7774…ee47

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcf972a29…1a35

0x065c9d…c394

3 touches
1 conflict

0xe6b7554c…ceca

0x065c9d…c394

3 touches
1 conflict

0x949bc521…2e49

0x065c9d…c394

2 touches
0 conflicts

0xb70e3ad4…8a3a

0x065c9d…c394

2 touches
0 conflicts

0xcef8190d…4c74

0x065c9d…c394

2 touches
0 conflicts

0xd4978a8e…dcf7

0x065c9d…c394

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 0x192b77746a…8fee47

← previous block·next block →recent activity