← previous blocknext block →recent activity

Analyzing

Block #72,267,203

31 transactions · 21 stateful · 2026-05-04 00:20:49 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.97

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,267,203  ·  31 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xeff080d8…b342

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xabe44c5a…1d8e

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

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: 0xd32edf66…9fff58

28 conflicts on slot 0xeff080d864…88b342

← previous block·next block →recent activity