Block #70,996,752

← previous blocknext block →recent activity

Analyzing

Block #70,996,752

10 transactions · 10 stateful · 2026-04-28 03:11:18 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,996,752  ·  10 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

0xa24509af…b379

0x065c9d…c394

4 touches
1 conflict

0xe9494884…9cbd

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x14f47665…3d59

0x065c9d…c394

4 touches
1 conflict

0x416c2ecf…af46

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbbac06c5…f9b0

0x065c9d…c394

2 touches
1 conflict

0x68510731…6ac9

0x065c9d…c394

2 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 0xa24509aff8…5cb379

← previous block·next block →recent activity