Block #71,244,249

← previous blocknext block →recent activity

Analyzing

Block #71,244,249

19 transactions · 15 stateful · 2026-04-29 06:38:56 UTC

Parallelism

68/100

Blocked

40%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,244,249  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0772f0ba…3f6a

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xfac61869…a55e

0x1b6862…e19c

4 touches
1 conflict

0xe870e232…7369

0x2a3755…a5a6

4 touches
1 conflict

0x825863c9…719e

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x552038…9fa4

4 touches
1 conflict

0x6cd8c5ab…af50

0x552038…9fa4

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

15 conflicts on slot 0x0772f0bada…f23f6a

← previous block·next block →recent activity