← previous blocknext block →recent activity

Analyzing

Block #72,497,038

9 transactions · 8 stateful · 2026-05-05 01:53:32 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,497,038  ·  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

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x041ee703…b4c1

0x34b655…2a6f

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x2d5e3771…9a87

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity