Block #71,172,163

← previous blocknext block →recent activity

Analyzing

Block #71,172,163

10 transactions · 10 stateful · 2026-04-28 22:39:25 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x23951077…539b

0x34b655…2a6f

4 touches
1 conflict

0xcbad3868…f129

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x322b74fc…4dbb

0x065c9d…c394

2 touches
0 conflicts

0x5bb486d0…f4c2

0x065c9d…c394

2 touches
0 conflicts

0x5e775529…ea72

0x065c9d…c394

2 touches
0 conflicts

0xde0857d8…6eca

0x065c9d…c394

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