← previous blocknext block →recent activity

Analyzing

Block #72,284,825

9 transactions · 8 stateful · 2026-05-04 02:19:14 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,284,825  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

4 touches
1 conflict

0x96aa7e47…f584

0x34b655…2a6f

4 touches
1 conflict

0xa800bb04…1d40

0x34b655…2a6f

4 touches
1 conflict

0xc389d1ff…6a00

0x34b655…2a6f

4 touches
1 conflict

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x109d8a52…a7b7

0x34b655…2a6f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity