Block #70,996,068

← previous blocknext block →recent activity

Analyzing

Block #70,996,068

12 transactions · 12 stateful · 2026-04-28 03:06:45 UTC

Parallelism

83/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,996,068  ·  12 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

0x13fb143f…8415

0x065c9d…c394

4 touches
1 conflict

0x2c547f25…82bf

0x065c9d…c394

4 touches
1 conflict

0x3d6202a5…4b1e

0x065c9d…c394

4 touches
1 conflict

0x801bc856…fa2b

0x065c9d…c394

4 touches
1 conflict

0x82625377…12eb

0x065c9d…c394

4 touches
1 conflict

0xddafe75a…3d7a

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

1 conflict on slot 0x13fb143fd0…c88415

← previous block·next block →recent activity