← previous blocknext block →recent activity

Analyzing

Block #71,595,324

7 transactions · 6 stateful · 2026-04-30 21:41:38 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,595,324  ·  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

0x109d8a52…a7b7

0x34b655…2a6f

4 touches
1 conflict

0xe4af4c87…9964

0x34b655…2a6f

4 touches
1 conflict

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x0453c706…ae71

0x34b655…2a6f

2 touches
0 conflicts

0x0a809ce1…7894

0x34b655…2a6f

2 touches
0 conflicts

0x42f11bc6…a231

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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

1 conflict on slot 0x109d8a5293…02a7b7

← previous block·next block →recent activity