Block #72,221,286

← previous blocknext block →recent activity

Analyzing

Block #72,221,286

7 transactions · 6 stateful · 2026-05-03 19:12:17 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,221,286  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xea7f2e45…f6f2

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x44a6edf2…0dde

0x065c9d…c394

3 touches
1 conflict

0x5118b0ba…75f3

0x065c9d…c394

3 touches
1 conflict

0x4b7eacc4…b18d

0x065c9d…c394

2 touches
0 conflicts

0xdf4c37f9…56a8

0x065c9d…c394

2 touches
0 conflicts

0xfa95c964…d915

0x065c9d…c394

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

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 0xea7f2e45a2…50f6f2

← previous block·next block →recent activity