← previous blocknext block →recent activity

Analyzing

Block #73,922,229

12 transactions · 12 stateful · 2026-05-11 16:17:47 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,922,229  ·  12 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xa5134d7c…d28e

0xd32edf…ff58

3 touches
1 conflict

0x55eb0c75…643a

0x065c9d…c394

2 touches
0 conflicts

0x5d48082c…081a

0x065c9d…c394

2 touches
0 conflicts

0x8049e0e1…d94a

0x065c9d…c394

2 touches
0 conflicts

0xaea3ed41…58ea

0x065c9d…c394

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity