Block #72,860,012

← previous blocknext block →recent activity

Analyzing

Block #72,860,012

28 transactions · 27 stateful · 2026-05-06 18:12:48 UTC

Parallelism

50/100

Blocked

70%

Avg conflicts / tx

3.61

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #72,860,012  ·  28 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

24 touches
66 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

22 touches
55 conflicts

0xc6417de0…2191

0xc8689a…ee79

20 touches
45 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

20 touches
45 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

20 touches
45 conflicts

0x32ee90db…decc

0x34b655…2a6f

20 touches
45 conflicts

0xac8e97a0…8426

0x34b655…2a6f

20 touches
45 conflicts

0xecd3dd4f…0f84

0x34b655…2a6f

14 touches
21 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

66 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity