Block #71,244,306

← previous blocknext block →recent activity

Analyzing

Block #71,244,306

13 transactions · 11 stateful · 2026-04-29 06:39:18 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,244,306  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x37cfaf01…4a46

0x34b655…2a6f

4 touches
1 conflict

0x3eadb0b6…d2f7

0x34b655…2a6f

4 touches
1 conflict

0xb378025c…30cf

0x34b655…2a6f

4 touches
1 conflict

0x5d8373b9…233d

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233e

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233f

0x44b60b…f711

2 touches
0 conflicts

0x8956cb26…42f7

0x44b60b…f711

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity