Block #71,070,613

← previous blocknext block →recent activity

Analyzing

Block #71,070,613

10 transactions · 10 stateful · 2026-04-28 11:22:59 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,070,613  ·  10 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

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb80

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x25f0aac9…d3c8

0xd32edf…ff58

3 touches
1 conflict

0x99236bda…2305

0x065c9d…c394

2 touches
0 conflicts

0xb6144afb…f471

0x065c9d…c394

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000012

← previous block·next block →recent activity