← previous blocknext block →recent activity

Analyzing

Block #71,065,126

8 transactions · 7 stateful · 2026-04-28 10:46:22 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,065,126  ·  8 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

0x2c1d5fa8…2446

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xac80483e…884c

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x5508a0d8…986b

0x065c9d…c394

4 touches
1 conflict

0xf89a87e0…803b

0x065c9d…c394

4 touches
1 conflict

0xe036c1fd…accc

0x065c9d…c394

4 touches
1 conflict

0x2f80b223…34cb

0x065c9d…c394

3 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 0x2c1d5fa8b1…1d2446

← previous block·next block →recent activity