Block #70,995,111

← previous blocknext block →recent activity

Analyzing

Block #70,995,111

13 transactions · 11 stateful · 2026-04-28 03:00:22 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,995,111  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x3702b140…97ea

0x34b655…2a6f

4 touches
1 conflict

0x3ba34a4e…a580

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x4c4307ef…b98a

0x34b655…2a6f

4 touches
1 conflict

0x5ce2465f…c4f1

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

3 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity