← previous blocknext block →recent activity

Analyzing

Block #73,651,204

21 transactions · 16 stateful · 2026-05-10 09:59:16 UTC

Parallelism

57/100

Blocked

63%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,651,204  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xa91c899f…6ee3

0x34b655…2a6f

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xaed1fa0f…08fa

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

8 touches
6 conflicts

0xedb848fe…6534

0x34b655…2a6f

8 touches
6 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

28 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity