Block #71,416,617

← previous blocknext block →recent activity

Analyzing

Block #71,416,617

18 transactions · 13 stateful · 2026-04-30 01:47:34 UTC

Parallelism

72/100

Blocked

62%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,416,617  ·  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

0xe3a73274…6514

0xd32edf…ff58

9 touches
10 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x794a7ac5…7190

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x266b9916…0cd8

0x065c9d…c394

3 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

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: 0xd32edf66…9fff58

10 conflicts on slot 0xe3a7327429…526514

← previous block·next block →recent activity