← previous blocknext block →recent activity

Analyzing

Block #73,655,217

10 transactions · 10 stateful · 2026-05-10 10:26:20 UTC

Parallelism

60/100

Blocked

40%

Avg conflicts / tx

0.8

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,655,217  ·  10 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x2c264710…365c

0xa6afd3…d132

3 touches
1 conflict

0x1a9e4505…24c6

0xd32edf…ff58

3 touches
1 conflict

0x00cd934f…a3e4

0x188d58…ea8e

2 touches
0 conflicts

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0x4e368b2b…09ac

0x754704…b603

2 touches
0 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity