Block #70,951,533

← previous blocknext block →recent activity

Analyzing

Block #70,951,533

15 transactions · 14 stateful · 2026-04-27 22:10:00 UTC

Parallelism

60/100

Blocked

43%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,951,533  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xd11dc26e…59ab

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x3d34f2bd…5d63

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x764f2d09…bc43

0x34b655…2a6f

4 touches
1 conflict

0x9af2f5e8…b43f

0x34b655…2a6f

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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity