Block #71,000,380

← previous blocknext block →recent activity

Analyzing

Block #71,000,380

8 transactions · 7 stateful · 2026-04-28 03:35:23 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,000,380  ·  8 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x188a7cc8…f2e9

0x065c9d…c394

4 touches
1 conflict

0xfc77d13f…ad4b

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x65e795ca…0320

0x34b655…2a6f

2 touches
0 conflicts

0x80737f78…d8c8

0x34b655…2a6f

2 touches
0 conflicts

0x8aa1941d…2988

0x34b655…2a6f

2 touches
0 conflicts

0xac206e47…ef7d

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity