Block #71,094,521

← previous blocknext block →recent activity

Analyzing

Block #71,094,521

10 transactions · 10 stateful · 2026-04-28 14:02:18 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,094,521  ·  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

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0xfefd1e1d…5fed

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xdb781596…01ae

0x754704…b603

2 touches
0 conflicts

0x56cf5c23…a88b

0xa6afd3…d132

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: 0x188d586d…f9ea8e

1 conflict on slot 0xe75ce68176…09ba61

← previous block·next block →recent activity