← previous blocknext block →recent activity

Analyzing

Block #71,065,035

15 transactions · 13 stateful · 2026-04-28 10:45:46 UTC

Parallelism

67/100

Blocked

31%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,065,035  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe2667cf9…66c8

0x065c9d…c394

7 touches
6 conflicts

0x11b69a7e…334e

0xee8c0e…1242

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

6 touches
3 conflicts

0x513f566d…2f28

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbfa3e821…53a4

0xd32edf…ff58

3 touches
1 conflict

0x7a079794…fc3b

0x0594c7…a3be

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

6 conflicts on slot 0xe2667cf9e1…4a66c8

← previous block·next block →recent activity