← previous blocknext block →recent activity

Analyzing

Block #71,066,020

12 transactions · 11 stateful · 2026-04-28 10:52:20 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,066,020  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x81ba238f…5fb4

0x065c9d…c394

4 touches
1 conflict

0x992c8689…92bb

0x065c9d…c394

3 touches
1 conflict

0xef76896f…0c56

0x065c9d…c394

3 touches
1 conflict

0xe22aad9a…aa01

0x065c9d…c394

2 touches
0 conflicts

0x00000000…00c9

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa88

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity