← previous blocknext block →recent activity

Analyzing

Block #72,817,281

24 transactions · 17 stateful · 2026-05-06 13:27:50 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,817,281  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0x578e7f66…1b56

0x34b655…2a6f

8 touches
6 conflicts

0x9b0235a2…a1dc

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x2e90dcf9…1289

0x34b655…2a6f

6 touches
3 conflicts

0x9dc9fa5f…7f23

0x34b655…2a6f

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

10 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity