← previous blocknext block →recent activity

Analyzing

Block #71,697,315

7 transactions · 5 stateful · 2026-05-01 09:00:30 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,697,315  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x882f9b0b…d062

0x065c9d…c394

4 touches
1 conflict

0x3ad8e1a3…ab2a

0x065c9d…c394

3 touches
1 conflict

0xf956b205…393e

0x065c9d…c394

3 touches
1 conflict

0x26e3b357…51e6

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xb079168a…75ea

0x065c9d…c394

2 touches
0 conflicts

0xe497a010…4f3a

0x065c9d…c394

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