← previous blocknext block →recent activity

Analyzing

Block #72,233,740

37 transactions · 25 stateful · 2026-05-03 20:35:54 UTC

Parallelism

76/100

Blocked

72%

Avg conflicts / tx

1.27

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,233,740  ·  37 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x2da22020…d441

0xd32edf…ff58

7 touches
6 conflicts

0x2ed00f98…da9f

0x34b655…2a6f

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x1c389468…6b0e

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity