Block #71,743,163

← previous blocknext block →recent activity

Analyzing

Block #71,743,163

24 transactions · 18 stateful · 2026-05-01 14:05:48 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,743,163  ·  24 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

0x267aa8b7…75d8

0xd32edf…ff58

13 touches
21 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x0abfa31c…c13e

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x90d24713…b88d

0x1b6862…e19c

4 touches
1 conflict

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

21 conflicts on slot 0x267aa8b722…ac75d8

← previous block·next block →recent activity