Block #71,095,322

← previous blocknext block →recent activity

Analyzing

Block #71,095,322

27 transactions · 22 stateful · 2026-04-28 14:07:39 UTC

Parallelism

67/100

Blocked

59%

Avg conflicts / tx

1.22

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,095,322  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x77441a68…ee1a

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x41755291…977f

0x131a2e…0da9

6 touches
3 conflicts

0xa1087a5c…66c4

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity