Block #71,558,983

← previous blocknext block →recent activity

Analyzing

Block #71,558,983

10 transactions · 10 stateful · 2026-04-30 17:39:48 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,558,983  ·  10 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

0x6cb1ffaf…7433

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbac3f9c4…4d9f

0x065c9d…c394

3 touches
1 conflict

0x262bc469…7c72

0x065c9d…c394

3 touches
1 conflict

0x0eadeeab…60f6

0x065c9d…c394

2 touches
0 conflicts

0x4186de24…90dc

0x065c9d…c394

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

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 0x6cb1ffaf1f…277433

← previous block·next block →recent activity