← previous blocknext block →recent activity

Analyzing

Block #73,610,378

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

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,610,378  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…000b

0x91e70e…30d8

2 touches
0 conflicts

0x00000000…0002

0xab3526…fa38

2 touches
0 conflicts

0x1a6fae96…79e2

0xacc0a0…fd62

2 touches
0 conflicts

0x7686841a…190a

0xacc0a0…fd62

2 touches
0 conflicts

0xbe37a690…b9ce

0xacc0a0…fd62

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity