Block #71,094,893

← previous blocknext block →recent activity

Analyzing

Block #71,094,893

11 transactions · 11 stateful · 2026-04-28 14:04:47 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,094,893  ·  11 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

0x5e0a06a4…8b73

0x065c9d…c394

4 touches
1 conflict

0x847d3d42…1338

0x065c9d…c394

4 touches
1 conflict

0xcff52d26…5c05

0x065c9d…c394

4 touches
1 conflict

0xdcadc17e…eb69

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0028

0x1b6862…e19c

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: 0x065c9d28…a9c394

1 conflict on slot 0x5e0a06a486…6e8b73

← previous block·next block →recent activity