← previous blocknext block →recent activity

Analyzing

Block #70,955,931

10 transactions · 9 stateful · 2026-04-27 22:39:17 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,955,931  ·  10 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

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x1925244e…7a94

0x188d58…ea8e

2 touches
0 conflicts

0x1925244e…7a95

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5e

0x188d58…ea8e

2 touches
0 conflicts

0x37608aa2…2169

0x188d58…ea8e

2 touches
0 conflicts

0x37608aa2…216a

0x188d58…ea8e

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

1 conflict on slot 0xbad6855239…f0e6bf

← previous block·next block →recent activity