Block #70,996,233

← previous blocknext block →recent activity

Analyzing

Block #70,996,233

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

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,996,233  ·  11 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

0xd4040564…3585

0x065c9d…c394

4 touches
1 conflict

0xe0a5ac8b…3d19

0x065c9d…c394

4 touches
1 conflict

0xe7e7fd3f…455c

0x065c9d…c394

4 touches
1 conflict

0xf86300c2…ad42

0x065c9d…c394

4 touches
1 conflict

0x8956cb26…42fa

0x73ada1…8be0

4 touches
1 conflict

0xf4e554ca…1a6c

0x73ada1…8be0

4 touches
1 conflict

0x1b4df54f…7afb

0x754704…b603

4 touches
1 conflict

0xa3dc6f35…13e9

0x754704…b603

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 0xd40405647b…283585

← previous block·next block →recent activity