← previous blocknext block →recent activity

Analyzing

Block #71,092,778

21 transactions · 18 stateful · 2026-04-28 13:50:41 UTC

Parallelism

81/100

Blocked

22%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,092,778  ·  21 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

0xcf35cfb0…cfd9

0xd32edf…ff58

7 touches
6 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x1becf377…c6f3

0xa6afd3…d132

3 touches
1 conflict

0x7f975651…8c28

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x00000000…0003

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0000

0x094452…0a09

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: 0xd32edf66…9fff58

6 conflicts on slot 0xcf35cfb04f…50cfd9

← previous block·next block →recent activity