← previous blocknext block →recent activity

Analyzing

Block #71,696,453

11 transactions · 7 stateful · 2026-05-01 08:54:47 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,696,453  ·  11 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

0xcaadfe3b…f14f

0x065c9d…c394

4 touches
1 conflict

0x68851a97…aacb

0x065c9d…c394

4 touches
1 conflict

0xc046d227…4f91

0xd32edf…ff58

3 touches
1 conflict

0xbba08bb1…e46a

0x065c9d…c394

3 touches
1 conflict

0x29be1c9d…6a88

0x065c9d…c394

2 touches
0 conflicts

0x32c48a7e…5028

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

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