← previous blocknext block →recent activity

Analyzing

Block #72,271,351

38 transactions · 27 stateful · 2026-05-04 00:48:41 UTC

Parallelism

79/100

Blocked

56%

Avg conflicts / tx

0.74

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,271,351  ·  38 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x0db14e1b…e8df

0xd32edf…ff58

7 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd2a4f525…d9c2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf6c9bf9b…ac02

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x7e9d3a…9fda

6 touches
3 conflicts

0xd59f6ed1…03e4

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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity