← previous blocknext block →recent activity

Analyzing

Block #72,856,124

26 transactions · 20 stateful · 2026-05-06 17:46:56 UTC

Parallelism

81/100

Blocked

60%

Avg conflicts / tx

0.96

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,856,124  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3b8ffd61…f3ad

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x1ee7a8f7…87f4

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0x3b8ffd6160…92f3ad

← previous block·next block →recent activity