← previous blocknext block →recent activity

Analyzing

Block #72,285,661

18 transactions · 14 stateful · 2026-05-04 02:24:53 UTC

Parallelism

72/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,285,661  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x8a85cf3d…2868

0x34b655…2a6f

4 touches
1 conflict

0xa8bd52b5…862e

0x34b655…2a6f

4 touches
1 conflict

0xb96e29a5…0419

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

6 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity