Block #71,095,319

← previous blocknext block →recent activity

Analyzing

Block #71,095,319

24 transactions · 19 stateful · 2026-04-28 14:07:38 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,095,319  ·  24 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

0x082a13aa…7310

0xd32edf…ff58

9 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xed863ec8…90d6

0x1b6862…e19c

6 touches
3 conflicts

0x4848d1ba…38fa

0x065c9d…c394

5 touches
3 conflicts

0xfaed8e86…b380

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

10 conflicts on slot 0x082a13aa11…047310

← previous block·next block →recent activity