Block #70,862,305

← previous blocknext block →recent activity

Analyzing

Block #70,862,305

15 transactions · 11 stateful · 2026-04-27 12:15:54 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,862,305  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x907866d4…e67f

0xd32edf…ff58

5 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xad125e8b…e519

0x065c9d…c394

3 touches
1 conflict

0xfe452053…6b43

0x065c9d…c394

3 touches
1 conflict

0x00000000…0006

0x010592…1c83

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: 0xd32edf66…9fff58

3 conflicts on slot 0x907866d4c9…eee67f

← previous block·next block →recent activity