← previous blocknext block →recent activity

Analyzing

Block #72,284,749

34 transactions · 23 stateful · 2026-05-04 02:18:43 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,284,749  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

6 touches
3 conflicts

0xd89f212d…2bbf

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x55b6a001…1e7a

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity