← previous blocknext block →recent activity

Analyzing

Block #73,753,182

22 transactions · 11 stateful · 2026-05-10 21:27:22 UTC

Parallelism

86/100

Blocked

36%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,753,182  ·  22 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

0x56a064ab…6c7d

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x9ef83c66…4437

0x34b655…2a6f

4 touches
1 conflict

0xfac43f12…b842

0x34b655…2a6f

4 touches
1 conflict

0xd06cc746…27e4

0x350035…7777

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

1 conflict on slot 0x56a064ab7e…fd6c7d

← previous block·next block →recent activity