← previous blocknext block →recent activity

Analyzing

Block #72,856,177

22 transactions · 15 stateful · 2026-05-06 17:47:17 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,856,177  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6e70c43d…c66e

0xd32edf…ff58

11 touches
15 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xb148bd15…738d

0x065c9d…c394

3 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0x9a555477…19a8

0x754704…b603

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: 0xd32edf66…9fff58

15 conflicts on slot 0x6e70c43d25…18c66e

← previous block·next block →recent activity