← previous blocknext block →recent activity

Analyzing

Block #71,070,064

17 transactions · 13 stateful · 2026-04-28 11:19:18 UTC

Parallelism

88/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,070,064  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1630ed91…9774

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0036

0x386489…7508

2 touches
0 conflicts

0xe61e5e93…e72f

0x386489…7508

2 touches
0 conflicts

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

1 conflict on slot 0x1630ed917d…159774

← previous block·next block →recent activity