← previous blocknext block →recent activity

Analyzing

Block #71,709,310

12 transactions · 10 stateful · 2026-05-01 10:20:14 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,709,310  ·  12 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7d564c82…b3f1

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe4af4c87…9964

0x34b655…2a6f

4 touches
1 conflict

0x5d6da397…6c5c

0x34b655…2a6f

4 touches
1 conflict

0x6a53b1c0…c3f2

0x34b655…2a6f

4 touches
1 conflict

0x5ad5cdc5…a511

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42f7

0x73ada1…8be0

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity