← previous blocknext block →recent activity

Analyzing

Block #73,338,573

17 transactions · 14 stateful · 2026-05-08 23:17:12 UTC

Parallelism

82/100

Blocked

43%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,338,573  ·  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

0x23951077…539b

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0xedb848fe…6534

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0xa90e52fe…7eb1

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 0x2395107727…b6539b

← previous block·next block →recent activity