Block #70,995,439

← previous blocknext block →recent activity

Analyzing

Block #70,995,439

15 transactions · 12 stateful · 2026-04-28 03:02:33 UTC

Parallelism

87/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,995,439  ·  15 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

0x33d1bc92…264b

0x065c9d…c394

4 touches
1 conflict

0x37768a7d…f268

0x065c9d…c394

4 touches
1 conflict

0x558f4da9…1005

0x065c9d…c394

4 touches
1 conflict

0x55a98d10…375d

0x065c9d…c394

4 touches
1 conflict

0x657047d7…693c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3282f217…90ed

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

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 0x33d1bc9272…52264b

← previous block·next block →recent activity