Block #71,089,920

← previous blocknext block →recent activity

Analyzing

Block #71,089,920

12 transactions · 10 stateful · 2026-04-28 13:31:39 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,089,920  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x5d8373b9…233d

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233e

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233f

0x44b60b…f711

2 touches
0 conflicts

0x8956cb26…42f7

0x44b60b…f711

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 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: 0x065c9d28…a9c394

1 conflict on slot 0xf3d7a307cc…f14d63

← previous block·next block →recent activity