← previous blocknext block →recent activity

Analyzing

Block #73,683,214

9 transactions · 8 stateful · 2026-05-10 13:35:21 UTC

Parallelism

44/100

Blocked

50%

Avg conflicts / tx

1.11

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,683,214  ·  9 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf84821eb…8b8e

0x065c9d…c394

4 touches
1 conflict

0x59bccea3…5ffb

0x065c9d…c394

4 touches
1 conflict

0xbe1ca643…7005

0x065c9d…c394

2 touches
0 conflicts

0xc3a97e75…1228

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity