Block #71,070,098

← previous blocknext block →recent activity

Analyzing

Block #71,070,098

25 transactions · 24 stateful · 2026-04-28 11:19:32 UTC

Parallelism

84/100

Blocked

54%

Avg conflicts / tx

0.8

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,070,098  ·  25 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

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 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: 0xb857c13a…1a9be1

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity