← previous blocknext block →recent activity

Analyzing

Block #72,267,205

14 transactions · 13 stateful · 2026-05-04 00:20:49 UTC

Parallelism

79/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,267,205  ·  14 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

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0xb2fa6dfd…51ea

0x065c9d…c394

2 touches
0 conflicts

0x8e1f1cdc…b721

0x122c0d…e3fa

2 touches
0 conflicts

0xe0e05ae3…4b41

0x122c0d…e3fa

2 touches
0 conflicts

0x04981db8…6d37

0x2a68ba…90c5

2 touches
0 conflicts

0x00f245ce…1e10

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: 0x065c9d28…a9c394

1 conflict on slot 0x4175529119…79977f

← previous block·next block →recent activity