Block #70,918,068

← previous blocknext block →recent activity

Analyzing

Block #70,918,068

6 transactions · 6 stateful · 2026-04-27 18:27:17 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,918,068  ·  6 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

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1b0

0x8d66a4…3095

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x26f91c0d…ce1f

0x34b655…2a6f

2 touches
0 conflicts

0x47ad3002…f9aa

0x34b655…2a6f

2 touches
0 conflicts

0x678143da…dc6b

0x34b655…2a6f

2 touches
0 conflicts

0x6c042c61…f883

0x34b655…2a6f

2 touches
0 conflicts

0x6eba5e7f…4b52

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 0x7f430e471f…4e4cbd

← previous block·next block →recent activity