← previous blocknext block →recent activity

Analyzing

Block #72,859,227

16 transactions · 13 stateful · 2026-05-06 18:07:34 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,859,227  ·  16 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0x4ebc357f…2635

0x065c9d…c394

4 touches
1 conflict

0xa11a8d3b…f04a

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0003

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0004

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0005

0x0594c7…a3be

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity