← previous blocknext block →recent activity

Analyzing

Block #73,705,531

28 transactions · 20 stateful · 2026-05-10 16:05:46 UTC

Parallelism

82/100

Blocked

50%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,705,531  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf0f5892c…1d99

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

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: 0xd32edf66…9fff58

10 conflicts on slot 0xf0f5892c26…891d99

← previous block·next block →recent activity