Block #71,683,790

← previous blocknext block →recent activity

Analyzing

Block #71,683,790

7 transactions · 7 stateful · 2026-05-01 07:30:26 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,683,790  ·  7 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

0xb6af401e…b071

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9dc696c5…10af

0x065c9d…c394

4 touches
1 conflict

0xf62cdcd1…e2c8

0x065c9d…c394

3 touches
1 conflict

0xa71dcf47…880f

0x065c9d…c394

3 touches
1 conflict

0x1a9d636e…0a67

0x065c9d…c394

3 touches
1 conflict

0x39ca29de…ee7a

0x065c9d…c394

3 touches
1 conflict

0x1a4b4152…0a08

0x33663b…4897

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 0xb6af401e53…5ab071

← previous block·next block →recent activity