← previous blocknext block →recent activity

Analyzing

Block #73,804,726

29 transactions · 24 stateful · 2026-05-11 03:15:02 UTC

Parallelism

62/100

Blocked

71%

Avg conflicts / tx

2.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,804,726  ·  29 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

20 touches
45 conflicts

0x0fa5e7bf…a4da

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x99f080dc…58c1

0x34b655…2a6f

10 touches
10 conflicts

0x9be2b99a…a959

0x34b655…2a6f

10 touches
10 conflicts

0x9db64d13…fb98

0x34b655…2a6f

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0xb378025c…30cf

0x34b655…2a6f

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

45 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity