← previous blocknext block →recent activity

Analyzing

Block #71,065,895

14 transactions · 12 stateful · 2026-04-28 10:51:30 UTC

Parallelism

64/100

Blocked

42%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,065,895  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xf0493190…b20b

0x065c9d…c394

6 touches
3 conflicts

0xa920ff4a…eb2c

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x324cb0fe…02df

0x065c9d…c394

4 touches
1 conflict

0x5ef20b9e…eb9b

0x065c9d…c394

4 touches
1 conflict

0xac0a8f7f…d4d5

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x131a2e…0da9

4 touches
1 conflict

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity