← previous blocknext block →recent activity

Analyzing

Block #71,092,705

32 transactions · 26 stateful · 2026-04-28 13:50:12 UTC

Parallelism

81/100

Blocked

62%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,092,705  ·  32 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb3bb3722…5612

0xd32edf…ff58

11 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x11f25e19…8bb1

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

15 conflicts on slot 0xb3bb3722be…c95612

← previous block·next block →recent activity