← previous blocknext block →recent activity

Analyzing

Block #71,036,804

11 transactions · 11 stateful · 2026-04-28 07:37:51 UTC

Parallelism

36/100

Blocked

64%

Avg conflicts / tx

1.55

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,036,804  ·  11 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8d2e781d…3404

0xd32edf…ff58

11 touches
15 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0x4dcfec16…8617

0x065c9d…c394

3 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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

15 conflicts on slot 0x8d2e781d21…a43404

← previous block·next block →recent activity