← previous blocknext block →recent activity

Analyzing

Block #73,648,529

14 transactions · 14 stateful · 2026-05-10 09:41:17 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,648,529  ·  14 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

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0xa904c4d7…675d

0x34b655…2a6f

6 touches
3 conflicts

0x96d90bc7…cb12

0x34b655…2a6f

6 touches
3 conflicts

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

0x34b655…2a6f

4 touches
1 conflict

0xa8bd52b5…862e

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

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

6 conflicts on slot 0x15d039e716…294bb6

← previous block·next block →recent activity