← previous blocknext block →recent activity

Analyzing

Block #71,042,687

22 transactions · 20 stateful · 2026-04-28 08:16:59 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,042,687  ·  22 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity