Block #71,555,869

← previous blocknext block →recent activity

Analyzing

Block #71,555,869

20 transactions · 17 stateful · 2026-04-30 17:19:00 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,555,869  ·  20 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

0xdaa6d130…d24a

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x8fa0889f…0346

0x34b655…2a6f

4 touches
1 conflict

0x9a3801b1…a598

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

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

6 conflicts on slot 0xdaa6d1306b…e6d24a

← previous block·next block →recent activity