← previous blocknext block →recent activity

Analyzing

Block #71,172,868

10 transactions · 10 stateful · 2026-04-28 22:44:07 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,172,868  ·  10 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

0x86f469ab…a0b3

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x99a4bd33…aa12

0x065c9d…c394

4 touches
1 conflict

0x9bdad9d3…9890

0x065c9d…c394

4 touches
1 conflict

0xeed941dd…0d5d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf298c368…a481

0x1efe02…37d6

2 touches
0 conflicts

0x00000000…0099

0xaa3145…feec

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

1 conflict on slot 0x86f469ab0b…4ea0b3

← previous block·next block →recent activity