← previous blocknext block →recent activity

Analyzing

Block #72,856,166

34 transactions · 28 stateful · 2026-05-06 17:47:13 UTC

Parallelism

68/100

Blocked

54%

Avg conflicts / tx

1.47

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,856,166  ·  34 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

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0xecd3dd4f…0f84

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x5aeaf08b…cbf7

0x34b655…2a6f

10 touches
10 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

8 touches
6 conflicts

0x32ee90db…decc

0x34b655…2a6f

6 touches
3 conflicts

0x3638e1ad…ec0e

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

21 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity