← previous blocknext block →recent activity

Analyzing

Block #73,655,079

9 transactions · 7 stateful · 2026-05-10 10:25:24 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x4f220769…4d55

0x065c9d…c394

3 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0xed2a929a…5365

0x065c9d…c394

2 touches
0 conflicts

0x5a1cd68f…4125

0x754704…b603

2 touches
0 conflicts

0xa1087a5c…66c4

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