← previous blocknext block →recent activity

Analyzing

Block #73,697,310

24 transactions · 18 stateful · 2026-05-10 15:10:17 UTC

Parallelism

83/100

Blocked

56%

Avg conflicts / tx

0.79

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,697,310  ·  24 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

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x4b570998…defa

0xd32edf…ff58

7 touches
6 conflicts

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

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 0xf2438038b6…475fa7

← previous block·next block →recent activity