← previous blocknext block →recent activity

Analyzing

Block #73,648,894

19 transactions · 14 stateful · 2026-05-10 09:43:43 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.74

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,648,894  ·  19 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0xf3808e5a…dbfb

0x34b655…2a6f

7 touches
6 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0520da1d…c88e

0x34b655…2a6f

6 touches
3 conflicts

0x689cd5fd…5556

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity