← previous blocknext block →recent activity

Analyzing

Block #73,660,811

20 transactions · 16 stateful · 2026-05-10 11:04:00 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x38524fae…9deb

0x34b655…2a6f

8 touches
6 conflicts

0x388f889f…a655

0x34b655…2a6f

6 touches
3 conflicts

0x7b2f9a78…47b9

0x34b655…2a6f

6 touches
3 conflicts

0xd40bddc1…773c

0x34b655…2a6f

6 touches
3 conflicts

0x8cace3cd…b871

0x34b655…2a6f

6 touches
3 conflicts

0xa2a9347c…3a0a

0x34b655…2a6f

6 touches
3 conflicts

0xa3ff1ab2…8ae3

0x34b655…2a6f

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

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

6 conflicts on slot 0x38524faed4…ae9deb

← previous block·next block →recent activity