← previous blocknext block →recent activity

Analyzing

Block #73,660,864

17 transactions · 16 stateful · 2026-05-10 11:04:22 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,660,864  ·  17 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x14845934…d13c

0x34b655…2a6f

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity