Block #70,892,203

← previous blocknext block →recent activity

Analyzing

Block #70,892,203

24 transactions · 19 stateful · 2026-04-27 15:34:58 UTC

Parallelism

79/100

Blocked

63%

Avg conflicts / tx

1.04

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,892,203  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0xe6bc2705…d15b

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0x9418c6aa…5a67

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xaf498679…7732

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity