← previous blocknext block →recent activity

Analyzing

Block #71,089,882

34 transactions · 30 stateful · 2026-04-28 13:31:24 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,089,882  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf3d7a307…4d63

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4546ebad…b908

0x34b655…2a6f

6 touches
3 conflicts

0xa67e6c87…37ca

0xd32edf…ff58

5 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