Block #71,065,386

← previous blocknext block →recent activity

Analyzing

Block #71,065,386

8 transactions · 6 stateful · 2026-04-28 10:48:07 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,065,386  ·  8 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

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x75f6889e…7f1e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x199d2ea8…8cc3

0x065c9d…c394

2 touches
0 conflicts

0x222ae6f9…c592

0x065c9d…c394

2 touches
0 conflicts

0xac9fc41c…e8bc

0x065c9d…c394

2 touches
0 conflicts

0xe1ef7276…c14b

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity