← previous blocknext block →recent activity

Analyzing

Block #73,696,242

9 transactions · 9 stateful · 2026-05-10 15:03:05 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,696,242  ·  9 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xb54e03d0…f33e

0x065c9d…c394

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x471d1e55…25ed

0x065c9d…c394

2 touches
0 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity