← previous blocknext block →recent activity

Analyzing

Block #71,042,691

17 transactions · 15 stateful · 2026-04-28 08:17:01 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,042,691  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x131a2e…0da9

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x51ecdf19…e365

0x065c9d…c394

4 touches
1 conflict

0xfdbf8549…cb2c

0x065c9d…c394

3 touches
1 conflict

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity