← previous blocknext block →recent activity

Analyzing

Block #73,961,373

9 transactions · 9 stateful · 2026-05-11 20:38:06 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,961,373  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0006

0x2ab50b…5c41

2 touches
0 conflicts

0x05b8ccbb…46bc

0x2ab50b…5c41

2 touches
0 conflicts

0x06d60e39…4ebd

0x2ab50b…5c41

2 touches
0 conflicts

0x0e2253bb…88e2

0x2ab50b…5c41

2 touches
0 conflicts

0x0ffd9cbf…f9c5

0x2ab50b…5c41

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity