← previous blocknext block →recent activity

Analyzing

Block #73,867,616

11 transactions · 9 stateful · 2026-05-11 10:14:00 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,867,616  ·  11 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0xf3e9e2d2…89ce

0x065c9d…c394

4 touches
1 conflict

0x99c5f9bf…2ffa

0x065c9d…c394

3 touches
1 conflict

0xb1d6f076…a3c5

0x065c9d…c394

3 touches
1 conflict

0x62164e0c…44b4

0x065c9d…c394

2 touches
0 conflicts

0x7ffb8381…1c63

0x065c9d…c394

2 touches
0 conflicts

0x89e57cf5…95d6

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity