← previous blocknext block →recent activity

Analyzing

Block #71,065,901

8 transactions · 6 stateful · 2026-04-28 10:51:33 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,065,901  ·  8 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

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x324cb0fe…02df

0x065c9d…c394

2 touches
0 conflicts

0x5ef20b9e…eb9b

0x065c9d…c394

2 touches
0 conflicts

0x62a41566…7b8f

0x065c9d…c394

2 touches
0 conflicts

0xac0a8f7f…d4d5

0x065c9d…c394

2 touches
0 conflicts

0xb559d7bd…4eae

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