Block #72,167,104

← previous blocknext block →recent activity

Analyzing

Block #72,167,104

33 transactions · 27 stateful · 2026-05-03 13:08:12 UTC

Parallelism

88/100

Blocked

52%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,167,104  ·  33 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x7d29d6f0…63fd

0xd32edf…ff58

7 touches
6 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

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

6 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity