← previous blocknext block →recent activity

Analyzing

Block #73,660,803

20 transactions · 15 stateful · 2026-05-10 11:03:57 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,660,803  ·  20 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

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x38524fae…9deb

0x34b655…2a6f

6 touches
3 conflicts

0xb7cf6a4e…8d4b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xe01158fd…f980

0x1b6862…e19c

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0xb91a6f59b9…c8722c

← previous block·next block →recent activity