← previous blocknext block →recent activity

Analyzing

Block #73,846,359

9 transactions · 8 stateful · 2026-05-11 07:52:06 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,846,359  ·  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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0006

0x2ab50b…5c41

2 touches
0 conflicts

0x006a9d46…6d59

0x2ab50b…5c41

2 touches
0 conflicts

0x039fd5ab…0d4f

0x2ab50b…5c41

2 touches
0 conflicts

0x05b8ccbb…46bc

0x2ab50b…5c41

2 touches
0 conflicts

0x05c32cec…11f6

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity