← previous blocknext block →recent activity

Analyzing

Block #71,065,162

12 transactions · 11 stateful · 2026-04-28 10:46:37 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,065,162  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x1ea44869…70fb

0x065c9d…c394

4 touches
1 conflict

0xbc90b85d…81e9

0x065c9d…c394

4 touches
1 conflict

0xc0a6feef…c424

0x065c9d…c394

4 touches
1 conflict

0x540cefe1…b57c

0x065c9d…c394

3 touches
1 conflict

0xf2da887c…dc63

0x065c9d…c394

3 touches
1 conflict

0x8ad6fe79…1a2a

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 0x0000000000…00003d

← previous block·next block →recent activity