Block #70,995,913

← previous blocknext block →recent activity

Analyzing

Block #70,995,913

7 transactions · 7 stateful · 2026-04-28 03:05:43 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xc73c4bfa…c144

0x8d66a4…3095

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xcd5c7f64…ad4b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0004

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

3 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

3 touches
1 conflict

0x03924cd3…f268

0x8d66a4…3095

3 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

2 touches
0 conflicts

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: 0x8d66a43f…113095

1 conflict on slot 0xc73c4bfabc…1fc144

← previous block·next block →recent activity