← previous blocknext block →recent activity

Analyzing

Block #72,817,398

38 transactions · 30 stateful · 2026-05-06 13:28:37 UTC

Parallelism

74/100

Blocked

63%

Avg conflicts / tx

1.68

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #72,817,398  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0x00000000…0002

0x7e9d3a…9fda

12 touches
15 conflicts

0x61ad45b1…15ac

0x34b655…2a6f

10 touches
10 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0xac8e97a0…8426

0x34b655…2a6f

8 touches
6 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

8 touches
6 conflicts

0x32ee90db…decc

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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity