Block #70,917,746

← previous blocknext block →recent activity

Analyzing

Block #70,917,746

8 transactions · 7 stateful · 2026-04-27 18:25:08 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,917,746  ·  8 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x6c162f6b…c0b8

0x34b655…2a6f

2 touches
0 conflicts

0xd1d608ec…d3bb

0x34b655…2a6f

2 touches
0 conflicts

0xd895ee0b…d301

0x34b655…2a6f

2 touches
0 conflicts

0xe8f5e33f…719c

0x34b655…2a6f

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity