← previous blocknext block →recent activity

Analyzing

Block #71,070,029

14 transactions · 13 stateful · 2026-04-28 11:19:05 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,070,029  ·  14 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

0x93d20a5d…b465

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x03b2f56d…1a03

0x065c9d…c394

3 touches
1 conflict

0xdf620278…4dc7

0x065c9d…c394

3 touches
1 conflict

0xee709f9c…f529

0x065c9d…c394

3 touches
1 conflict

0x00000000…0006

0x60bb42…87ea

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

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 0x93d20a5d1e…04b465

← previous block·next block →recent activity