← previous blocknext block →recent activity

Analyzing

Block #71,094,433

18 transactions · 15 stateful · 2026-04-28 14:01:42 UTC

Parallelism

72/100

Blocked

40%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,094,433  ·  18 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x00000000…0000

0xc1a578…8e1a

4 touches
1 conflict

0x00000000…0001

0xc1a578…8e1a

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0028

0x1b6862…e19c

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity