Block #72,855,781

← previous blocknext block →recent activity

Analyzing

Block #72,855,781

14 transactions · 13 stateful · 2026-05-06 17:44:40 UTC

Parallelism

64/100

Blocked

31%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,855,781  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

8 touches
6 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

8 touches
6 conflicts

0x32ee90db…decc

0x34b655…2a6f

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0xac8e97a0…8426

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: 0xc8689a47…62ee79

6 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity