Block #70,877,751

← previous blocknext block →recent activity

Analyzing

Block #70,877,751

11 transactions · 9 stateful · 2026-04-27 13:58:47 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,877,751  ·  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

0x0cce0daa…9d52

0x065c9d…c394

4 touches
1 conflict

0x4c06bb7a…3e1c

0x065c9d…c394

4 touches
1 conflict

0x71c854be…16cb

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x032c41ac…c35a

0x065c9d…c394

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1b0

0x8d66a4…3095

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 0x0cce0daab7…379d52

← previous block·next block →recent activity