Block #70,996,438

← previous blocknext block →recent activity

Analyzing

Block #70,996,438

17 transactions · 11 stateful · 2026-04-28 03:09:12 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,996,438  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x432bfdd0…4ca0

0x065c9d…c394

3 touches
1 conflict

0x35d9a523…b36b

0x065c9d…c394

3 touches
1 conflict

0xa3ea3bad…605b

0x065c9d…c394

3 touches
1 conflict

0x856b5c2e…8484

0x065c9d…c394

3 touches
1 conflict

0x8956cb26…42fd

0x73ada1…8be0

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity