Block #70,986,424

← previous blocknext block →recent activity

Analyzing

Block #70,986,424

7 transactions · 6 stateful · 2026-04-28 02:02:29 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,986,424  ·  7 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

0xe70bdebb…626e

0x065c9d…c394

4 touches
1 conflict

0xde066967…d7fb

0x065c9d…c394

4 touches
1 conflict

0xa7cc43e5…d2e5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xffa781b3…3029

0x065c9d…c394

4 touches
1 conflict

0x73c15e8f…b6a7

0x065c9d…c394

4 touches
1 conflict

0x44aaac5a…f244

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 0xe70bdebbe5…69626e

← previous block·next block →recent activity