Block #71,422,197

← previous blocknext block →recent activity

Analyzing

Block #71,422,197

14 transactions · 12 stateful · 2026-04-30 02:24:42 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,422,197  ·  14 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

0x5f1f6e08…201f

0x188d58…ea8e

4 touches
1 conflict

0xbd0080d7…9a73

0x188d58…ea8e

4 touches
1 conflict

0xa800bb04…1d40

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

2 touches
0 conflicts

0x21d22421…0b7a

0x34b655…2a6f

2 touches
0 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

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 0x5f1f6e086d…ff201f

← previous block·next block →recent activity