← previous blocknext block →recent activity

Analyzing

Block #73,748,859

23 transactions · 12 stateful · 2026-05-10 20:58:13 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,748,859  ·  23 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

0x15d039e7…4bb6

0x34b655…2a6f

6 touches
3 conflicts

0xa8e512cf…ba71

0x34b655…2a6f

6 touches
3 conflicts

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x3e88a45b…9e29

0x34b655…2a6f

4 touches
1 conflict

0x65115257…9813

0x34b655…2a6f

4 touches
1 conflict

0xa8bd52b5…862e

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

3 conflicts on slot 0x15d039e716…294bb6

← previous block·next block →recent activity