← previous blocknext block →recent activity

Analyzing

Block #72,284,727

18 transactions · 14 stateful · 2026-05-04 02:18:34 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,284,727  ·  18 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a6

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a7

0x8d66a4…3095

4 touches
1 conflict

0x87150585…01f3

0x065c9d…c394

4 touches
1 conflict

0x893cd52c…5766

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity