Block #71,696,843

← previous blocknext block →recent activity

Analyzing

Block #71,696,843

12 transactions · 11 stateful · 2026-05-01 08:57:24 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,696,843  ·  12 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb3720c01…a52d

0x065c9d…c394

4 touches
1 conflict

0xff1c015f…74f1

0x065c9d…c394

3 touches
1 conflict

0x382ab4a3…990c

0x065c9d…c394

3 touches
1 conflict

0x6d79558a…8804

0x065c9d…c394

2 touches
0 conflicts

0x86f469ab…a0b3

0x065c9d…c394

2 touches
0 conflicts

0x8e3ad403…3381

0x065c9d…c394

2 touches
0 conflicts

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 0x0000000000…00003d

← previous block·next block →recent activity